Welcome, Guest. Please login or register.
Did you miss your activation email?
Friday 27 December 2024, 11:41:09 pm

Login with username, password and session length

Get the new Updates directly from Endian  HERE
14262 Posts in 4377 Topics by 6517 Members
Latest Member: Sandro
Search:     Advanced search
+  EFW Support
|-+  Support
| |-+  General Support
| | |-+  IO broken on 2.4
0 Members and 0 Guests are viewing this topic. « previous next »
Pages: [1] Go Down Print
Author Topic: IO broken on 2.4  (Read 25669 times)
deadmalc
Full Member
***
Offline Offline

Posts: 36


« on: Wednesday 09 June 2010, 05:32:45 am »

After a bit more digging I'm convinced that postfix is broken in 2.4
I use it with authentication to the primary mail server, and after an email with an attachment the system hangs.
Really bizarre, I can ssh to the server but if i try and vi a file vi hangs, anything with file I/O seems to be broken.
Think I will migrate that off to another dmz box, and see if the problem still occurs.
Anyone else seen this issue?
Logged
deadmalc
Full Member
***
Offline Offline

Posts: 36


« Reply #1 on: Wednesday 09 June 2010, 05:00:25 pm »

Nope issue is still reocurring without postfix, what a strange crash.
No logs, nothing just frozen IO on the box
Logged
nico.prenzel
Full Member
***
Offline Offline

Posts: 10


« Reply #2 on: Wednesday 09 June 2010, 06:05:38 pm »

I've got almost the same error (postifx isn't involved here).
The EFW 2.4 stops doing anything IO related. After a  of time it resumes as nothing had happened.
One good thing about that. It happens rarely. I can't specify it more exactly.
Crazy.

Logged
deadmalc
Full Member
***
Offline Offline

Posts: 36


« Reply #3 on: Thursday 10 June 2010, 05:22:43 pm »

It doesn't happen to me all the time, but about once a day. Which means if I'm not there to forcefully shut the box off (a reboot will not work)
then we can't send email (postfix), or use the web (squid) but the firewall still processes traffic.
If I try to use the web interface, that jams as well.

Anyone have any ideas how to debug this?
Logged
nico.prenzel
Full Member
***
Offline Offline

Posts: 10


« Reply #4 on: Thursday 10 June 2010, 06:25:50 pm »

Today, the Endian Team released another bunch of upgrades to the EFW 2.4 community version. Perhaps, these changes does have effect at the IO freeze bug.

I do also remember that the freeze IO error happened at the very first usage of the EFW 2.4. It has been reproduceable then some services (for me OpenVPN) had been restarted by the web GUI. But this behaviour is also gone for now.

Does your IO freeze happen each day at the same time (pherhaps some cron action)?
Logged
deadmalc
Full Member
***
Offline Offline

Posts: 36


« Reply #5 on: Thursday 10 June 2010, 11:01:27 pm »

Cheers for the note about updates, I've updated and running 2.4 again to see what happens.
The main way it hung was sending an attachment (word document) through postfix. That seemed to kill it, not every time.
Sometimes, it will just randomly freeze - most of the time it's because email has gone and killed it.

Still getting that dodgy segfault though  Cry

kernel: [  221.707812] fetchipac[6972]: segfault at 1 ip b75f7e16 sp bf9902e8 error 4 in libc-2.3.4.so[b75a4000+114000]

Well we shall see if that is any better! Lets hope so.

I've also noticed pdflush using a hell a lot of cpu every so often (possibly nothing as this is running of a file storage rather than dedicated storage)
Logged
nico.prenzel
Full Member
***
Offline Offline

Posts: 10


« Reply #6 on: Thursday 10 June 2010, 11:26:52 pm »

Today, the Endian Team also fixed the segfault of ipac. At least there bugfix database shows that. Hopefully there would be another upgrade!?

I've searched for pdflush and found that:
Quote
pdflush is for flushing out dirty buffers to disk. If however you have
little RAM and lots of swap it may indeed thrash for a little while while
doing this task.

Pherhaps you should increase your RAM. I'll also look at my EFW and look at the pdflush performance. If i do remember correctly my EFW does have 512 MB RAM assigned.

Logged
nico.prenzel
Full Member
***
Offline Offline

Posts: 10


« Reply #7 on: Thursday 10 June 2010, 11:38:15 pm »

On more... pherhaps your machine runs out of free memory because of a potential memory leak (pherhaps, again related to the segfault of ipac)!

One goal of pdflush is to write dirty pages to disk under low memory conditions.

Read there:
freeweb.hu/linuxkernel2/ch15lev1sec4.html
Logged
deadmalc
Full Member
***
Offline Offline

Posts: 36


« Reply #8 on: Thursday 10 June 2010, 11:52:37 pm »

Plenty of memory free (2Gb assigned), 0 swap used (I only have 100MB of swap, due to a cockup in my calculation with fdisk)
Think this is just my dodgy on filesystem partition in kvm I use for testing
Logged
nico.prenzel
Full Member
***
Offline Offline

Posts: 10


« Reply #9 on: Thursday 10 June 2010, 11:54:52 pm »

pity, it seemed to be such a nice explanation.
Logged
deadmalc
Full Member
***
Offline Offline

Posts: 36


« Reply #10 on: Friday 11 June 2010, 02:48:53 am »

Day one finished after the efw-upgrade and no problems so far....cross fingers!
Logged
deadmalc
Full Member
***
Offline Offline

Posts: 36


« Reply #11 on: Friday 11 June 2010, 06:07:42 pm »

Seems the postfix problem is still lurking there :-(

Restarting postfix causes the hash on /etc/aliases to hang and amavisd will not shutdown

After shutting postfix down fine, and attempting to restart it....

root      9239  9212  0 08:03 pts/0    00:00:00 /bin/bash /etc/init.d/postfix
start
root      9244  9239  0 08:03 pts/0    00:00:00 /usr/sbin/postalias hash
/etc/aliases


root@saaflanfirewall:/var/log # /etc/init.d/amavisd stop
Shutting down Mail Virus Scanner (amavisd):                [  OK  ]
ps -efroot@saaflanfirewall:/var/log # ps -ef|fgrep amavis
amavis    5416     1  0 07:07 ?        00:00:00 amavisd (ch1-finish)
amavis    5417     1  0 07:07 ?        00:00:00 amavisd (ch0-finish)
amavis    5418     1  0 07:07 ?        00:00:00 amavisd (ch0-finish)
amavis    5419     1  0 07:07 ?        00:00:00 amavisd (ch0-finish)
amavis    5421     1  0 07:07 ?        00:00:00 amavisd (ch0-finish)
amavis    5423     1  0 07:07 ?        00:00:00 amavisd (ch0-finish)
amavis    5424     1  0 07:07 ?        00:00:00 amavisd (ch0-finish)
amavis    5427     1  0 07:07 ?        00:00:00 amavisd (ch0-finish)
amavis    5429     1  0 07:07 ?        00:00:00 amavisd (ch0-finish)
amavis    5430     1  0 07:07 ?        00:00:00 amavisd (ch0-finish)
amavis    5431     1  0 07:07 ?        00:00:00 amavisd (ch0-finish)
root      9456  9212  0 08:03 pts/0    00:00:00 fgrep amavis


root@saaflanfirewall:/var/log # killall amavisd
root@saaflanfirewall:/var/log # killall amavisd
root@saaflanfirewall:/var/log # killall amavisd
root@saaflanfirewall:/var/log # killall -9 amavisd
root@saaflanfirewall:/var/log # killall -9 amavisd
root@saaflanfirewall:/var/log # killall -9 amavisd
root@saaflanfirewall:/var/log # killall -9 amavisd
root@saaflanfirewall:/var/log # ps -ef|fgrep amavis
amavis    5416     1  0 07:06 ?        00:00:00 amavisd (ch1-finish)
amavis    5417     1  0 07:06 ?        00:00:00 amavisd (ch0-finish)
amavis    5418     1  0 07:06 ?        00:00:00 amavisd (ch0-finish)
amavis    5419     1  0 07:06 ?        00:00:00 amavisd (ch0-finish)
amavis    5421     1  0 07:06 ?        00:00:00 amavisd (ch0-finish)
amavis    5423     1  0 07:06 ?        00:00:00 amavisd (ch0-finish)
amavis    5424     1  0 07:06 ?        00:00:00 amavisd (ch0-finish)
amavis    5427     1  0 07:06 ?        00:00:00 amavisd (ch0-finish)
amavis    5429     1  0 07:06 ?        00:00:00 amavisd (ch0-finish)
amavis    5430     1  0 07:06 ?        00:00:00 amavisd (ch0-finish)
amavis    5431     1  0 07:06 ?        00:00:00 amavisd (ch0-finish)

root      9239  9212  0 07:56 pts/0    00:00:00 /bin/bash /etc/init.d/postfix
start
root      9244  9239  0 07:56 pts/0    00:00:00 /usr/sbin/postalias hash
/etc/aliases
root      9468  9212  0 08:03 pts/0    00:00:00 ps -ef
root@saaflanfirewall:/var/log # kill 9244
root@saaflanfirewall:/var/log # kill 9244
root@saaflanfirewall:/var/log # kill 9244
root@saaflanfirewall:/var/log # kill -9 9244
root@saaflanfirewall:/var/log # kill -9 9244
root@saaflanfirewall:/var/log # kill -9 9244
root@saaflanfirewall:/var/log # ps -ef|fgrep postalias
root      9244  9239  0 07:56 pts/0    00:00:00 /usr/sbin/postalias hash
/etc/aliases
root      9470  9212  0 08:03 pts/0    00:00:00 fgrep postalias

Bug filed http://bugs.endian.com/view.php?id=2997
Logged
deadmalc
Full Member
***
Offline Offline

Posts: 36


« Reply #12 on: Friday 11 June 2010, 09:53:47 pm »

I've turned off virus mail scanning, see if that is the problem....
Still battling with it :-(
Logged
Pages: [1] Go Up Print 
« previous next »
Jump to:  

Page created in 0.125 seconds with 19 queries.
Powered by SMF 1.1 RC2 | SMF © 2001-2005, Lewis Media Design by 7dana.com