[arm-allstar] Apache not starting with boot

[David McGough]

Steve,

Check to make sure you're not out of space on any 
filesystems---particularly the /var/log filesystem, which is a tmpfs 
(ramdrive) filesystem. You can check used space with the df command, like:

[root at RPi4B-dev ~]# df
Filesystem                1K-blocks     Used Available Use% Mounted on
/dev/root                   3762048  1793044   1758184  51% /
devtmpfs                    1970284        0   1970284   0% /dev
tmpfs                       2004076        0   2004076   0% /dev/shm
tmpfs                       2004076    16656   1987420   1% /run
tmpfs                       2004076        0   2004076   0% /sys/fs/cgroup
tmpfs                       2004076     4080   1999996   1% /tmp
tmpfs                         51200      652     50548   2% /var/log
/dev/mmcblk0p1               102182    34346     67836  34% /boot


....Look at the "Use%" column, for values near or at 100%.

Note that if you've got the ssh server open without restriction to the
Internet on port 222, you *WILL* get attacked and the /var/log/btmp (bad
ssh login attempts) file will fill the /var/log filesystem up, causing a
DoS condition.

Since you mention that things work properly for a while after reboot, I'm
very suspect that /var/log is filling up.

73, David KB4FXC





On Wed, 6 May 2020, "Steve Polley via ARM-allstar" wrote:

> Doug,
> 
> Message I get when enabling the first command.
> 
> systemctl enable httpd
> Error getting authority: Error initializing authority: Error calling
> StartServiceByName for org.freedesktop.PolicyKit1:
> GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Failed to activate service
> 'org.freedesktop.PolicyKit1': timed out (g-dbus-error-quark, 20)
> 
> Second command
> 
>  systemctl start httpd
> Error getting authority: Error initializing authority: Error calling
> StartServiceByName for org.freedesktop.PolicyKit1: Timeout was reached
> (g-io-error-quark, 24)
> 
> A little more info...The supermon page will randomly quit working and a
> reboot will fix it but goes down after awhile.  Checking services running
> like the original post states that it is failed to run.  Again, a reboot
> will temporarily fix the issue.
> 
> Steve
> 
> 
> 
> On Wed, May 6, 2020 at 12:19 AM Steve Polley <stormchaselive at gmail.com>
> wrote:
> 
> > Doug,
> >
> > Just an FYI, I have had the same problem with one of my NODES as well.
> >
> > I will report back once I make these changes.
> >
> > Steve
> > N0SWP
> >
> > On Wed, May 6, 2020 at 12:05 AM "Doug Crompton via ARM-allstar" <
> > arm-allstar at hamvoip.org> wrote:
> >
> >> Also DO NOT put anything BEFORE the call to Allstar in  /etc/rc.local.
> >> This will cause timing issues and could cause miss loading of httpd.
> >>
> >> rc.local
> >>
> >> # Starts Allstar
> >>
> >> echo -1> /proc/sys/kernel/sched_rt_runtime_us
> >> /usr/local/etc/rc.allstar
> >>
> >> # any additions should go here or after
> >>
> >> Lets us know if this was the problem.
> >>
> >> *73 Doug, WA3DSP*
> >> *http://wa3dsp.org <http://wa3dsp.org>*
> >>
> >>
> >>
> >> *73 Doug*
> >>
> >> *WA3DSP*
> >>
> >> *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >>
> >>
> >> On Tue, May 5, 2020 at 11:27 PM Doug Crompton <wa3dsp at gmail.com> wrote:
> >>
> >> > Not sure why it would get this way but what you need to do is
> >> >
> >> > systemctl enable httpd
> >> > systemctl start httpd
> >> >
> >> > simply starting it is only for current boot. You need to enable it to
> >> > start at all future boots.  Some how it got disabled.
> >> >
> >> >
> >> > *73 Doug*
> >> >
> >> > *WA3DSP*
> >> >
> >> > *http://www.crompton.com/hamradio <http://www.crompton.com/hamradio>*
> >> >
> >> >
> >> > On Tue, May 5, 2020 at 6:31 PM "Brad Trogdon via ARM-allstar" <
> >> > arm-allstar at hamvoip.org> wrote:
> >> >
> >> >> Hello all I am running latest update of HamVoIP and have recently
> >> started
> >> >> having issue where my nodes supermom would not work.  Was driving me
> >> crazy
> >> >> until i tested to see if server was running and it was not.  a manual
> >> >> entry
> >> >> of systemctl enable httpd and systemctl start httpd solves the issue
> >> until
> >> >> the next reboot.
> >> >>
> >> >> a. Any clue why its not auto starting as my other nodes do?
> >> >> b. any hint where I can look to figure it out?
> >> >> c. if I cannot figure out should I just create a script to start upon
> >> >> reboot?
> >> >>
> >> >> thanks in advance for every ones assistance.
> >> >>
> >> >> -Brad
> >> >> ~~
> >> >> _______________________________________________
> >> >>
> >> >> ARM-allstar mailing list
> >> >> ARM-allstar at hamvoip.org
> >> >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >> >>
> >> >> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
> >> >>
> >> >
> >> _______________________________________________
> >>
> >> ARM-allstar mailing list
> >> ARM-allstar at hamvoip.org
> >> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> >>
> >> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
> >>
> >
> _______________________________________________
> 
> ARM-allstar mailing list
> ARM-allstar at hamvoip.org
> http://lists.hamvoip.org/cgi-bin/mailman/listinfo/arm-allstar
> 
> Visit the BBB and RPi2/3/4 web page - http://hamvoip.org
>