Tom Eastep wrote:> On Wed, 10 Mar 2004, Dominik Strnad wrote: > >> Hmmmm let''s rock, I need some more testing, but seems for now that >> redirecting all outputs - mean STDOUT and STDERR to /dev/null seems to >> help... >> >> But stil I realy dn''t know WHY! :-) >> > > Then I believe that you are running out of disk space. > > When you run an embedded OS disbribution on your firewall, you have to > expect these sorts of problems. It''s one of the reasons why I use a > "real" distribution on my firewall; it allows me to focus on > firewalling problems rather than on embedded OS limitations... > > -TomI''d be surprised if he is running out of disk space. Oddly enough, I see a similar problem at this end when running shorewall from a cronjob. Only difference is where shorewall restart "stops". At this end, my trace file shows... ++ echo /etc/shorewall/params + local user_exit=/etc/shorewall/params + ''['' -f /etc/shorewall/params '']'' + echo ''Processing /etc/shorewall/params ...'' and thats it. I had to manually restart shorewall to get things back to normal. I''ll keep checking some ideas I have at this end. Steve Cowles
On Tue, 9 Mar 2004, Cowles, Steve wrote:> Tom Eastep wrote: > > On Wed, 10 Mar 2004, Dominik Strnad wrote: > > > >> Hmmmm let''s rock, I need some more testing, but seems for now that > >> redirecting all outputs - mean STDOUT and STDERR to /dev/null seems to > >> help... > >> > >> But stil I realy dn''t know WHY! :-) > >> > > > > Then I believe that you are running out of disk space. > > > > When you run an embedded OS disbribution on your firewall, you have to > > expect these sorts of problems. It''s one of the reasons why I use a > > "real" distribution on my firewall; it allows me to focus on > > firewalling problems rather than on embedded OS limitations... > > > > -Tom > > I''d be surprised if he is running out of disk space. Oddly enough, I see a > similar problem at this end when running shorewall from a cronjob. Only > difference is where shorewall restart "stops". At this end, my trace file > shows... > > ++ echo /etc/shorewall/params > + local user_exit=/etc/shorewall/params > + ''['' -f /etc/shorewall/params '']'' > + echo ''Processing /etc/shorewall/params ...'' > > and thats it. I had to manually restart shorewall to get things back to > normal. > > I''ll keep checking some ideas I have at this end. >Thanks, Steve. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ teastep@shorewall.net
Tom Eastep wrote:> On Tue, 9 Mar 2004, Cowles, Steve wrote: > >> I''d be surprised if he is running out of disk space. Oddly enough, I >> see a similar problem at this end when running shorewall from a >> cronjob. Only difference is where shorewall restart "stops". At this >> end, my trace file shows... >> >> ++ echo /etc/shorewall/params >> + local user_exit=/etc/shorewall/params >> + ''['' -f /etc/shorewall/params '']'' >> + echo ''Processing /etc/shorewall/params ...'' >> >> and thats it. I had to manually restart shorewall to get things back >> to normal. >> >> I''ll keep checking some ideas I have at this end. >> > > Thanks, Steve.It''s getting late, but I am still unable to run a shorewall restart from a cronjob on my leaf system. I even tried running the restart using the bash shell instead of ash. Best I can tell (and I''m speculating here), its like the internal buffers (for stdout/stderr) on the leaf cronjob are filling up and can''t be flushed or something along those lines. I really don''t know. I even set the MAILTO varaiable in /etc/crontab. In fact, shorewall restart does not even show up when I issue ps aux after the restart stalls. Strange! This might be a good question for the leaf folks. Something seems unique about the crontab that is running on leaf. BTW: I was looking at some of the leaf supplied cronjobs. Most seem to redirect output to /dev/null. Steve Cowles
Steve, Thank you for your investigation. Tom sorry, this seems to be leaf problem, I am sorry for disturbing you. Best Regars Litin -----Original Message----- From: shorewall-users-bounces@lists.shorewall.net [mailto:shorewall-users-bounces@lists.shorewall.net] On Behalf Of Cowles, Steve Sent: Wednesday, March 10, 2004 6:09 AM To: ''Mailing List for Experienced Shorewall Users'' Subject: RE: [Shorewall-users] shorewall stuck after cron restart Tom Eastep wrote:> On Tue, 9 Mar 2004, Cowles, Steve wrote: > >> I''d be surprised if he is running out of disk space. Oddly enough, I >> see a similar problem at this end when running shorewall from a >> cronjob. Only difference is where shorewall restart "stops". At this >> end, my trace file shows... >> >> ++ echo /etc/shorewall/params >> + local user_exit=/etc/shorewall/params >> + ''['' -f /etc/shorewall/params '']'' >> + echo ''Processing /etc/shorewall/params ...'' >> >> and thats it. I had to manually restart shorewall to get things back >> to normal. >> >> I''ll keep checking some ideas I have at this end. >> > > Thanks, Steve.It''s getting late, but I am still unable to run a shorewall restart from a cronjob on my leaf system. I even tried running the restart using the bash shell instead of ash. Best I can tell (and I''m speculating here), its like the internal buffers (for stdout/stderr) on the leaf cronjob are filling up and can''t be flushed or something along those lines. I really don''t know. I even set the MAILTO varaiable in /etc/crontab. In fact, shorewall restart does not even show up when I issue ps aux after the restart stalls. Strange! This might be a good question for the leaf folks. Something seems unique about the crontab that is running on leaf. BTW: I was looking at some of the leaf supplied cronjobs. Most seem to redirect output to /dev/null. Steve Cowles _______________________________________________ Shorewall-users mailing list Post: Shorewall-users@lists.shorewall.net Subscribe/Unsubscribe: https://lists.shorewall.net/mailman/listinfo/shorewall-users Support: http://www.shorewall.net/support.htm FAQ: http://www.shorewall.net/FAQ.htm