Forum Discussion
John_Stewart_10
Dec 22, 2011Nimbostratus
BIG3D
We have an LTM running 10.2.3.112 code. We ran the big3d -v command and get the following: root@rndltmcore:Active] config big3d -v
big3d version
big3d Versi...
Alex__Applebaum
Jan 17, 2012Employee
Hi John,
I installed the EM big3d (10.4.0.1.0) on 10.2.3 and upgraded to 10.2.3 HF1 and didn't see the restart issue.
[root@ltm2:Active] config b version | head
Kernel:
Linux 2.6.18-164.11.1.el5.1.0.f5app
Package:
BIG-IP Version 10.2.3 123.0
Hotfix HF1 Edition
Hot fixes:
ID372864
ID372590
ID372804
[root@ltm2:Active] config ps -ef | egrep 'bin/big3d' | grep -v grep
root 3821 3802 0 17:11 ? S 0:00 /shared/bin/big3d
[root@ltm2:Active] config /shared/bin/big3d -v
/shared/bin/big3d version big3d Version 10.4.0.1.0 for linux
What I think may have happened is that a 2nd big3d process was started at the same time. For example, I accidently ran it again like:
[root@ltm2:Active] config /shared/bin/big3d
Jan 16 17:39:31 local/ltm2 emerg logger: Re-starting big3d
Jan 16 17:39:32 local/ltm2 emerg logger: Re-starting big3d
Jan 16 17:39:33 local/ltm2 emerg logger: Re-starting big3d
Jan 16 17:39:34 local/ltm2 emerg logger: Re-starting big3d
Jan 16 17:39:35 local/ltm2 emerg logger: Re-starting big3d
Jan 16 17:39:36 local/ltm2 emerg logger: Re-starting big3d
[root@ltm2:Active] config Jan 16 17:39:37 local/ltm2 emerg logger: Re-starting big3d
I hit Ctl-C and things returned to normal (with only default daemon running).
There is a Bug ID to make it exit/log if another instance running which might help in the future.
Bug 344228 - If big3d detects another big3d already running, exits without log message
So short of it is, both big3ds should run just fine on 10.2.3 HF1. You should have been able to bigstart stop big3d & bigstart start big3d and you would have been ok. However in order for MP not to complain again, you need to restore your MP big3d with higher version . Going forward, you should be able to re-discover or even copy from another unit that MP big3d (10.4.0.1.0) back to /shared/bin/ and get your MP back up and running. The one with latest timestamp wins so if you see the 10.2.3 HF1 "10.2.3.112.0" big3d pop back up as the running process, just
touch /shared/bin/big3d
Otherwise, please open a case (while your logs haven't rotated) so they can investigate further. Dev was looking at this post so just post the case and I can forward it to them.
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects