Forum Discussion
Big ip Offline and generates error messages that appear continuously
HELLO
after restarting all services with sys restart service all, the BIG IP 8900 go offline and the system daemons restart continuously: In addition, the console generates error messages that appear similar to the following example:
emerg logger: Re-starting asm emerg logger: Re-starting wamd emerg logger: Re-starting asm emerg logger: Re-starting wamd emerg logger: Re-starting asm emerg logger: Re-starting wamd
CAN YOU HELP ME!! WE HAVE CRITICAL CUSTOMER AND OUR SITE IS DOWN emerg logger: Re-starting asm emerg logger: Re-starting wamd emerg logger: Re-starting asm
Many thanks in advance
11 Replies
- nathe
Cirrocumulus
Dechir,
A couple of things. What version of TMOS are you running incl hotfix? Any log entries in var/log/ltm that might shed more light on things and do you have another volume you can boot into with the same TMOS version that you could restore a recent UCS onto?
Rgds N
- dechir_21483
Nimbostratus
So,
We are under 11.1.0 HF2 , bellow a part of asm log:
Feb 5 14:04:21 PFSSRVLB01 crit perl[7690]: 01310027:2: ASM subsystem error (recovery_mngr.pl,main::fatal_err): Can't exec '/usr/share/ts/bin/prepare_files.pl -site:1 -func:PrepareSiteFiles' Feb 5 14:04:21 PFSSRVLB01 notice (ts_proc)recovery_mngr.pl[7690]: (-2)(INIT_FAILED): calling sub 'prepare_files' encountered fatal error: 'Can't exec '/usr/share/ts/bin/prepare_files.pl -site:1 -func:PrepareSiteFiles'' Feb 5 14:04:27 PFSSRVLB01 crit perl[7927]: 01310027:2: ASM subsystem error (recovery_mngr.pl,main::fatal_err): Can't exec '/usr/share/ts/bin/prepare_files.pl -site:1 -func:PrepareSiteFiles' Feb 5 14:04:27 PFSSRVLB01 notice (ts_proc)recovery_mngr.pl[7927]: (-2)(INIT_FAILED): calling sub 'prepare_files' encountered fatal error: 'Can't exec '/usr/share/ts/bin/prepare_files.pl -site:1 -func:PrepareSiteFiles'' Feb 5 14:04:34 PFSSRVLB01 crit perl[8140]: 01310027:2: ASM subsystem error (recovery_mngr.pl,main::fatal_err): Can't exec '/usr/share/ts/bin/prepare_files.pl -site:1 -func:PrepareSiteFiles'
and I notice you that I have restore an old version but the problem persists.
Thank you .
- nathe
Cirrocumulus
Can you get to the GUI at all to run a qkview and upload to iHealth / F5 support?
I'd now probably try to build a new 11.1.0 volume, provision your modules, IP etc and then restore a UCS file. See if that works.
Else, if you unprovision ASM does the problem go away? Obviously if you need ASM then you'll need to re-provision it - this in itself may highlight an issue.
N
- >> CAN YOU HELP ME!! WE HAVE CRITICAL CUSTOMER AND OUR SITE IS DOWN then call support and have them help you, it is what they are there for. if you dont have the support contract then it is the right time to call your F5 reseller and get that worked out.
- dechir_21483
Nimbostratus
First, after disable ASM on Resource Provisioning(Non), the BIG IP reboot successufly and the problem disappeared and the big ip gone ONLINE but after re-enable ASM on Resource Provisionning(Nominal) the error reappear continuisly and the big ip gone Offline.
Concerning qkview I have uploaded it to iHealth:
Your software reached its End of Software Development (EoSD) date on Nov 28 2013. An upgrade is recommended
- dechir_21483
Nimbostratus
First, after disable ASM on Resource Provisioning(Non), the BIG IP reboot successufly and the problem disappeared and the big ip gone ONLINE but after re-enable ASM on Resource Provisionning(Nominal) the error reappear continuisly and the big ip gone Offline.
Concerning qkview I have uploaded it to iHealth:
Your software reached its End of Software Development (EoSD) date on Nov 28 2013. An upgrade is recommended
- nathe
Cirrocumulus
I agree - nitass
Employee
after re-enable ASM on Resource Provisionning(Nominal) the error reappear continuisly and the big ip gone Offline.
/var/log/asm should show something. if you cannot find it, as boneyard suggested, open a support case to get help from support engineer.
Your software reached its End of Software Development (EoSD) date on Nov 28 2013. An upgrade is recommended
if configuration is stable and you do not need any new feature in later software release, i do not think upgrading is really needed.
just my 2 cents.
- Izoc_161780
Nimbostratus
Hi Dechir,
Do you have any solution for this issue? unfortunately I have same issue. F5 maintenance support expired so i can't log the case.
Regards, Izoc
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)Recent Discussions
Related Content
* 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