lock_mlog shmget() failure

ciberpiano · ‎06-08-2011

What' s going on, since June 6 I have 4 Fortigates failed with lock_mlog output on console!!, what happed?

rwpatterson · ‎06-09-2011

What version of code were they running? Do they still function (as far as you know)?

Bob - self proclaimed posting junkie!
See my Fortigate related scripts at: http://fortigate.camerabob.com

Report Inappropriate Content · ‎06-10-2011

Hi, We have the same problem since June 8 with 2 Fortigate (60B and 50B). And internal interface doesn' t respond.

JnascECSI · ‎06-10-2011

I had the same problem on a 200B on wednesday that went unresponsive to all traffic and responses. I consoled in with a cable and it was erroring out with the following below error. Actually once i got in it that only lasted for about 2 minutes before it knocked me out and then would not respond to trying to reconnect. Basicilly it went limp and dead real fast. Pid-34 lock_mlog() -504 shmget()Failed: No Such File or Directory.

2 x FortiGate 200B 4.2.8 FortiGate 200A 4.2.8 FortiAnalyzer 100C 4.2.4 FortiAP 220B 4.2.7 FortiSwitch 80-POE 4.2.3

rwpatterson · ‎06-10-2011

See this post: http://support.fortinet.com/forum/tm.asp?m=73819&p=1&tmode=1&smode=1

Bob - self proclaimed posting junkie!
See my Fortigate related scripts at: http://fortigate.camerabob.com

Report Inappropriate Content · ‎06-14-2011

Again one Fortigate today (100A). I have read other post but we can' t " install HPQI Support Image via TFTP" or load firmware because Interface don' t respond.

ede_pfau · ‎06-14-2011

Connect to console port via serial cable. Reboot the FGT by power cycling. Immediately after the first messages on the console press any button to enter the Boot Menu. Here you can reload firmware or format the flash disk. IMHO you don' t need the HPQI special firmware - just reformat the flash disk, reload the current firmware via TFTP and restore the configuration.

Ede

"Kernel panic: Aiee, killing interrupt handler!"