Lasso 8.6 not starting automatically at startup

classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|

Lasso 8.6 not starting automatically at startup

Jussi Hirvi-2
Lasso 8.6.0, CentOS 5.10. When the system starts, Lasso tries to start.
It takes a long time, probably until some timeout (2 minutes?).

Then when I do
/etc/init.d/lasso8service status

It says that Lasso is stopped. It starts now normally on command
/etc/init.d/lasso8service start

Why can it be that it's not starting on system startup? There is nothing
on this in the system log (/var/log/messages) or
/usr/local/Lasso.../LassoErrors.txt.

- Jussi
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Lasso 8.6 not starting automatically at startup

decorior
Is Apache starting okay? I had an instance where Apache took a long time to start, and Lasso would fail. But once Apache was running it worked fine

Deco
On Jan 1, 2014, at 1:25 PM, Jussi Hirvi <[hidden email]> wrote:

> Lasso 8.6.0, CentOS 5.10. When the system starts, Lasso tries to start. It takes a long time, probably until some timeout (2 minutes?).
>
> Then when I do
> /etc/init.d/lasso8service status
>
> It says that Lasso is stopped. It starts now normally on command
> /etc/init.d/lasso8service start
>
> Why can it be that it's not starting on system startup? There is nothing on this in the system log (/var/log/messages) or /usr/local/Lasso.../LassoErrors.txt.
>
> - Jussi
> #############################################################
> This message is sent to you because you are subscribed to
> the mailing list Lasso [hidden email]
> Official list archives available at http://www.lassotalk.com
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Lasso 8.6 not starting automatically at startup

Jussi Hirvi-2
On 1.1.2014 22.53, deco rior wrote:
 > Is Apache starting okay? I had an instance where Apache took a long
 > time to start, and Lasso would fail. But once Apache was running it
 > worked fine

That was a good lead, though no success yet. Lasso was starting up
before Apache, so it was pretty obvious that it would fail.

I tried to fix by rearranging the startup scripts:
        cd /etc/rc.d/rc3.d
        mv S65lasso8service S99lasso8service
        reboot

(I am not sure if the original name started with S65, but anyway. Apache
startup script is S85httpd. )

Here is the end part of what I get on the console:

> Starting httpd: [  OK  ]
> Starting crond: [  OK  ]
> (...)
> Starting lasso8service:  Starting Lasso Service: Done
> [  OK  ]
> Starting webmin:  [  OK  ]
>
> CentOS release 5.10 (Final)
> Kernel 2.6.18-371.el5 on an x86_64
>
> myhost.mydomain.fi login:

Now Lasso tries to start after apache, but still it does not start
successfully, though it takes 2 minutes for it to try. I tested that the
startup script is ok by running manually after reboot (in the same dir
as above):
        sh S99lasso8service start

With this, lasso starts quite well. So I still don't know why Lasso does
not successfully start at startup.

- Jussi
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Lasso 8.6 not starting automatically at startup

stevepiercy
Within that runlevel, what do you get for:

     ls -al

Here's a known working example for CentOS 5.x:

# ls -al
total 8
drwxr-xr-x  2 root root 4096 Nov 20 15:02 .
drwxr-xr-x 10 root root 4096 Oct 21 05:38 ..
lrwxrwxrwx  1 root root   24 Jan 24  2012 K02avahi-dnsconfd -> ../init.d/avahi-dnsconfd
lrwxrwxrwx  1 root root   19 Jan 24  2012 K05saslauthd -> ../init.d/saslauthd
lrwxrwxrwx  1 root root   19 Jan 24  2012 K10dc_server -> ../init.d/dc_server
lrwxrwxrwx  1 root root   19 Jan 24  2012 K12dc_client -> ../init.d/dc_client
lrwxrwxrwx  1 root root   20 Jan 24  2012 K50netconsole -> ../init.d/netconsole
lrwxrwxrwx  1 root root   19 Jan 24  2012 K50snmptrapd -> ../init.d/snmptrapd
lrwxrwxrwx  1 root root   22 Oct 21 05:38 K74lvm2-monitor -> ../init.d/lvm2-monitor
lrwxrwxrwx  1 root root   15 Oct 21 05:38 K75netfs -> ../init.d/netfs
lrwxrwxrwx  1 root root   18 Jan 24  2012 K87mcstrans -> ../init.d/mcstrans
lrwxrwxrwx  1 root root   20 Jan 24  2012 K87multipathd -> ../init.d/multipathd
lrwxrwxrwx  1 root root   16 Jan 24  2012 K89iscsid -> ../init.d/iscsid
lrwxrwxrwx  1 root root   18 Jan 24  2012 K89netplugd -> ../init.d/netplugd
lrwxrwxrwx  1 root root   15 Jan 24  2012 K89rdisc -> ../init.d/rdisc
lrwxrwxrwx  1 root root   19 Jan 24  2012 K92ip6tables -> ../init.d/ip6tables
lrwxrwxrwx  1 root root   18 Jan 24  2012 S08iptables -> ../init.d/iptables
lrwxrwxrwx  1 root root   17 Oct 21 05:38 S10network -> ../init.d/network
lrwxrwxrwx  1 root root   21 Jan 24  2012 S12restorecond -> ../init.d/restorecond
lrwxrwxrwx  1 root root   16 Jan 24  2012 S12syslog -> ../init.d/syslog
lrwxrwxrwx  1 root root   15 Jan 24  2012 S13iscsi -> ../init.d/iscsi
lrwxrwxrwx  1 root root   15 Jan 24  2012 S13named -> ../init.d/named
lrwxrwxrwx  1 root root   20 Oct 21 05:38 S22messagebus -> ../init.d/messagebus
lrwxrwxrwx  1 root root   19 Jan 24  2012 S26haldaemon -> ../init.d/haldaemon
lrwxrwxrwx  1 root root   20 Jan 24  2012 S26lm_sensors -> ../init.d/lm_sensors
lrwxrwxrwx  1 root root   15 Jan 24  2012 S50snmpd -> ../init.d/snmpd
lrwxrwxrwx  1 root root   14 Jan 24  2012 S55sshd -> ../init.d/sshd
lrwxrwxrwx  1 root root   20 Jan 24  2012 S56rawdevices -> ../init.d/rawdevices
lrwxrwxrwx  1 root root   23 Jan 24  2012 S60lasso8service -> ../init.d/lasso8service
lrwxrwxrwx  1 root root   16 Jan 24  2012 S60vsftpd -> ../init.d/vsftpd
lrwxrwxrwx  1 root root   16 Jan 24  2012 S64mysqld -> ../init.d/mysqld
lrwxrwxrwx  1 root root   17 Jan 24  2012 S80postfix -> ../init.d/postfix
lrwxrwxrwx  1 root root   15 Jan 24  2012 S85httpd -> ../init.d/httpd
lrwxrwxrwx  1 root root   15 Jan 24  2012 S90crond -> ../init.d/crond
lrwxrwxrwx  1 root root   13 Jan 24  2012 S90xfs -> ../init.d/xfs
lrwxrwxrwx  1 root root   22 Jul 11 07:12 S97yum-updatesd -> ../init.d/yum-updatesd
lrwxrwxrwx  1 root root   22 Jan 24  2012 S98avahi-daemon -> ../init.d/avahi-daemon
lrwxrwxrwx  1 root root   15 Aug 15  2012 S98monit -> ../init.d/monit
lrwxrwxrwx  1 root root   11 Oct 21 05:38 S99local -> ../rc.local
lrwxrwxrwx  1 root root   18 Nov 20 15:02 S99webmin -> /etc/init.d/webmin

At initialization, the files beggining with 'S' will be started,
and the files beginning with 'K' will be killed.  To toggle an
item, make sure that the number after K and S sum to 100, e.g.:

     mv {K15,S85}httpd

To move an item's startup order:

     mv S{60,99}lasso8service # Set Lasso to start last

Some folks have reported issues with the default startup, so
they may startup services on which Lasso depends in the
following order:

ntpd
mysqld
httpd
lasso8service

--steve


On 1/2/14 at 4:35 AM, [hidden email] (Jussi Hirvi) pronounced:

>On 1.1.2014 22.53, deco rior wrote:
>>Is Apache starting okay? I had an instance where Apache took a long
>>time to start, and Lasso would fail. But once Apache was running it
>>worked fine
>
>That was a good lead, though no success yet. Lasso was starting
>up before Apache, so it was pretty obvious that it would fail.
>
>I tried to fix by rearranging the startup scripts:
>cd /etc/rc.d/rc3.d
>mv S65lasso8service S99lasso8service
>reboot
>
>(I am not sure if the original name started with S65, but
>anyway. Apache startup script is S85httpd. )
>
>Here is the end part of what I get on the console:
>
>>Starting httpd: [  OK  ]
>>Starting crond: [  OK  ]
>>(...)
>>Starting lasso8service:  Starting Lasso Service: Done
>>[  OK  ]
>>Starting webmin:  [  OK  ]
>>
>>CentOS release 5.10 (Final)
>>Kernel 2.6.18-371.el5 on an x86_64
>>
>>myhost.mydomain.fi login:
>
>Now Lasso tries to start after apache, but still it does not
>start successfully, though it takes 2 minutes for it to try. I
>tested that the startup script is ok by running manually after
>reboot (in the same dir as above):
>sh S99lasso8service start
>
>With this, lasso starts quite well. So I still don't know why
>Lasso does not successfully start at startup.
>
>- Jussi
>#############################################################
>This message is sent to you because you are subscribed to
>the mailing list Lasso [hidden email]
>Official list archives available at http://www.lassotalk.com
>To unsubscribe, E-mail to: <[hidden email]>
>Send administrative queries to  <[hidden email]>

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
Steve Piercy               Web Site Builder              
Soquel, CA
<[hidden email]>                  <http://www.StevePiercy.com/>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Lasso 8.6 not starting automatically at startup

Jussi Hirvi-2
On 2.1.2014 5.50, Steve Piercy - Web Site Builder wrote:

> At initialization, the files beggining with 'S' will be started, and the
> files beginning with 'K' will be killed.  To toggle an item, make sure
> that the number after K and S sum to 100, e.g.:
>
>      mv {K15,S85}httpd
>
> To move an item's startup order:
>
>      mv S{60,99}lasso8service # Set Lasso to start last
>
> Some folks have reported issues with the default startup, so they may
> startup services on which Lasso depends in the following order:
>
> ntpd
> mysqld
> httpd
> lasso8service

Ok. In your example Lasso (S60) starts before Apache (S85), so
apparently the order does not matter after all?

Below is my list.

- Jussi

[root@lasso2 ~]# cd /etc/rc.d/rc3.d/
[root@lasso2 rc3.d]# ls -al
lrwxrwxrwx  1 root root   17 Aug 24 08:29 K01dnsmasq -> ../init.d/dnsmasq
lrwxrwxrwx  1 root root   16 Aug 24 08:29 K01smartd -> ../init.d/smartd
lrwxrwxrwx  1 root root   24 Aug 24 08:29 K02avahi-dnsconfd ->
../init.d/avahi-dnsconfd
lrwxrwxrwx  1 root root   17 Aug 24 08:29 K02oddjobd -> ../init.d/oddjobd
lrwxrwxrwx  1 root root   22 Aug 24 08:29 K03yum-updatesd ->
../init.d/yum-updatesd
lrwxrwxrwx  1 root root   17 Aug 24 08:29 K05anacron -> ../init.d/anacron
lrwxrwxrwx  1 root root   13 Aug 24 08:29 K05atd -> ../init.d/atd
lrwxrwxrwx  1 root root   16 Aug 24 08:29 K05conman -> ../init.d/conman
lrwxrwxrwx  1 root root   19 Aug 24 08:29 K05saslauthd ->
../init.d/saslauthd
lrwxrwxrwx  1 root root   19 Aug 24 08:29 K10dc_server ->
../init.d/dc_server
lrwxrwxrwx  1 root root   16 Aug 24 08:29 K10psacct -> ../init.d/psacct
lrwxrwxrwx  1 root root   14 Aug 24 08:29 K10tcsd -> ../init.d/tcsd
lrwxrwxrwx  1 root root   19 Aug 24 08:29 K12dc_client ->
../init.d/dc_client
lrwxrwxrwx  1 root root   17 Dec 23 04:35 K12mailman -> ../init.d/mailman
lrwxrwxrwx  1 root root   13 Aug 24 08:29 K15gpm -> ../init.d/gpm
lrwxrwxrwx  1 root root   18 Aug 24 08:29 K15svnserve -> ../init.d/svnserve
lrwxrwxrwx  1 root root   13 Aug 24 08:29 K20nfs -> ../init.d/nfs
lrwxrwxrwx  1 root root   14 Aug 24 08:29 K24irda -> ../init.d/irda
lrwxrwxrwx  1 root root   20 Aug 24 08:29 K50netconsole ->
../init.d/netconsole
lrwxrwxrwx  1 root root   16 Dec 12 12:21 K50vsftpd -> ../init.d/vsftpd
lrwxrwxrwx  1 root root   20 Aug 24 08:29 K69rpcsvcgssd ->
../init.d/rpcsvcgssd
lrwxrwxrwx  1 root root   16 Aug 24 08:29 K72autofs -> ../init.d/autofs
lrwxrwxrwx  1 root root   16 Aug 24 08:29 K73ypbind -> ../init.d/ypbind
lrwxrwxrwx  1 root root   22 Oct 20 06:42 K74lvm2-monitor ->
../init.d/lvm2-monitor
lrwxrwxrwx  1 root root   14 Oct 20 06:41 K74nscd -> ../init.d/nscd
lrwxrwxrwx  1 root root   14 Aug 24 08:29 K74ntpd -> ../init.d/ntpd
lrwxrwxrwx  1 root root   15 Oct 20 06:42 K75netfs -> ../init.d/netfs
lrwxrwxrwx  1 root root   19 Aug 24 08:29 K85mdmonitor ->
../init.d/mdmonitor
lrwxrwxrwx  1 root root   15 Aug 24 08:29 K85mdmpd -> ../init.d/mdmpd
lrwxrwxrwx  1 root root   17 Aug 24 08:29 K85rpcgssd -> ../init.d/rpcgssd
lrwxrwxrwx  1 root root   19 Aug 24 08:29 K85rpcidmapd ->
../init.d/rpcidmapd
lrwxrwxrwx  1 root root   17 Aug 24 08:29 K86nfslock -> ../init.d/nfslock
lrwxrwxrwx  1 root root   20 Aug 24 08:29 K87irqbalance ->
../init.d/irqbalance
lrwxrwxrwx  1 root root   20 Aug 24 08:29 K87multipathd ->
../init.d/multipathd
lrwxrwxrwx  1 root root   16 Aug 24 08:29 K88auditd -> ../init.d/auditd
lrwxrwxrwx  1 root root   15 Aug 24 08:29 K88pcscd -> ../init.d/pcscd
lrwxrwxrwx  1 root root   24 Aug 24 08:29 K88wpa_supplicant ->
../init.d/wpa_supplicant
lrwxrwxrwx  1 root root   14 Aug 24 08:29 K89dund -> ../init.d/dund
lrwxrwxrwx  1 root root   15 Aug 24 08:29 K89iscsi -> ../init.d/iscsi
lrwxrwxrwx  1 root root   16 Aug 24 08:29 K89iscsid -> ../init.d/iscsid
lrwxrwxrwx  1 root root   18 Aug 24 08:29 K89netplugd -> ../init.d/netplugd
lrwxrwxrwx  1 root root   14 Aug 24 08:29 K89pand -> ../init.d/pand
lrwxrwxrwx  1 root root   15 Aug 24 08:29 K89rdisc -> ../init.d/rdisc
lrwxrwxrwx  1 root root   19 Aug 24 08:29 K90bluetooth ->
../init.d/bluetooth
lrwxrwxrwx  1 root root   19 Aug 24 08:29 K92ip6tables ->
../init.d/ip6tables
lrwxrwxrwx  1 root root   19 Aug 24 08:29 K95firstboot ->
../init.d/firstboot
lrwxrwxrwx  1 root root   15 Aug 24 08:29 K95kudzu -> ../init.d/kudzu
lrwxrwxrwx  1 root root   18 Aug 24 08:29 K99cpuspeed -> ../init.d/cpuspeed
lrwxrwxrwx  1 root root   25 Aug 24 08:29 K99readahead_later ->
../init.d/readahead_later
lrwxrwxrwx  1 root root   23 Aug 24 08:29 S00microcode_ctl ->
../init.d/microcode_ctl
lrwxrwxrwx  1 root root   25 Aug 24 08:29 S04readahead_early ->
../init.d/readahead_early
lrwxrwxrwx  1 root root   18 Aug 24 08:29 S08iptables -> ../init.d/iptables
lrwxrwxrwx  1 root root   18 Aug 24 08:29 S08mcstrans -> ../init.d/mcstrans
lrwxrwxrwx  1 root root   17 Oct 20 06:42 S10network -> ../init.d/network
lrwxrwxrwx  1 root root   21 Aug 24 08:29 S12restorecond ->
../init.d/restorecond
lrwxrwxrwx  1 root root   16 Aug 24 08:29 S12syslog -> ../init.d/syslog
lrwxrwxrwx  1 root root   15 Aug 24 08:29 S13named -> ../init.d/named
lrwxrwxrwx  1 root root   17 Aug 24 08:29 S13portmap -> ../init.d/portmap
lrwxrwxrwx  1 root root   20 Oct 20 06:43 S22messagebus ->
../init.d/messagebus
lrwxrwxrwx  1 root root   15 Aug 24 08:29 S26acpid -> ../init.d/acpid
lrwxrwxrwx  1 root root   19 Aug 24 08:29 S26haldaemon ->
../init.d/haldaemon
lrwxrwxrwx  1 root root   14 Aug 24 08:29 S26hidd -> ../init.d/hidd
lrwxrwxrwx  1 root root   14 Aug 24 08:29 S55sshd -> ../init.d/sshd
lrwxrwxrwx  1 root root   20 Aug 24 08:29 S56rawdevices ->
../init.d/rawdevices
lrwxrwxrwx  1 root root   15 Aug 24 08:29 S61clamd -> ../init.d/clamd
lrwxrwxrwx  1 root root   16 Aug 24 08:29 S64mysqld -> ../init.d/mysqld
lrwxrwxrwx  1 root root   24 Aug 24 08:29 S78amavisd-milter ->
../init.d/amavisd-milter
lrwxrwxrwx  1 root root   22 Aug 24 08:29 S78spamassassin ->
../init.d/spamassassin
lrwxrwxrwx  1 root root   17 Aug 24 08:29 S79amavisd -> ../init.d/amavisd
lrwxrwxrwx  1 root root   18 Aug 24 08:29 S80sendmail -> ../init.d/sendmail
lrwxrwxrwx  1 root root   15 Aug 24 08:29 S85httpd -> ../init.d/httpd
lrwxrwxrwx  1 root root   15 Aug 24 08:29 S90crond -> ../init.d/crond
lrwxrwxrwx  1 root root   13 Aug 24 08:29 S90xfs -> ../init.d/xfs
lrwxrwxrwx  1 root root   18 Aug 24 08:29 S92fail2ban -> ../init.d/fail2ban
lrwxrwxrwx  1 root root   22 Aug 24 08:29 S98avahi-daemon ->
../init.d/avahi-daemon
lrwxrwxrwx  1 root root   23 Aug 24 08:29 S99lasso8service ->
../init.d/lasso8service
lrwxrwxrwx  1 root root   11 Oct 20 06:42 S99local -> ../rc.local
lrwxrwxrwx  1 root root   16 Aug 24 08:29 S99webmin -> ../init.d/webmin
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Lasso 8.6 not starting automatically at startup

stevepiercy
On 1/2/14 at 1:51 PM, [hidden email] (Jussi Hirvi) pronounced:

>On 2.1.2014 5.50, Steve Piercy - Web Site Builder wrote:
>>At initialization, the files beggining with 'S' will be started, and the
>>files beginning with 'K' will be killed.  To toggle an item, make sure
>>that the number after K and S sum to 100, e.g.:
>>
>>mv {K15,S85}httpd
>>
>>To move an item's startup order:
>>
>>mv S{60,99}lasso8service # Set Lasso to start last
>>
>>Some folks have reported issues with the default startup, so they may
>>startup services on which Lasso depends in the following order:
>>
>>ntpd
>>mysqld
>>httpd
>>lasso8service
>
>Ok. In your example Lasso (S60) starts before Apache (S85), so
>apparently the order does not matter after all?

No.  It *might* matter.  My example works on my system, but
other folks have reported otherwise.

>Below is my list.

In your list below, ntpd is the only item that sticks out to me,
so I would enable it (unless it is enabled somewhere else).

     mv {K74,S26}ntpd

Other folks more sysadmin-y than I can probably pick out any
other issues.  This is one of those things that you set and forget.

I would also document the original stock configuration so I
would know how to unf* it.

--steve


>- Jussi
>
>[root@lasso2 ~]# cd /etc/rc.d/rc3.d/
>[root@lasso2 rc3.d]# ls -al
>lrwxrwxrwx  1 root root   17 Aug 24 08:29 K01dnsmasq -> ../init.d/dnsmasq
>lrwxrwxrwx  1 root root   16 Aug 24 08:29 K01smartd -> ../init.d/smartd
>lrwxrwxrwx  1 root root   24 Aug 24 08:29 K02avahi-dnsconfd -> ../init.d/avahi-dnsconfd
>lrwxrwxrwx  1 root root   17 Aug 24 08:29 K02oddjobd -> ../init.d/oddjobd
>lrwxrwxrwx  1 root root   22 Aug 24 08:29 K03yum-updatesd -> ../init.d/yum-updatesd
>lrwxrwxrwx  1 root root   17 Aug 24 08:29 K05anacron -> ../init.d/anacron
>lrwxrwxrwx  1 root root   13 Aug 24 08:29 K05atd -> ../init.d/atd
>lrwxrwxrwx  1 root root   16 Aug 24 08:29 K05conman -> ../init.d/conman
>lrwxrwxrwx  1 root root   19 Aug 24 08:29 K05saslauthd -> ../init.d/saslauthd
>lrwxrwxrwx  1 root root   19 Aug 24 08:29 K10dc_server -> ../init.d/dc_server
>lrwxrwxrwx  1 root root   16 Aug 24 08:29 K10psacct -> ../init.d/psacct
>lrwxrwxrwx  1 root root   14 Aug 24 08:29 K10tcsd -> ../init.d/tcsd
>lrwxrwxrwx  1 root root   19 Aug 24 08:29 K12dc_client -> ../init.d/dc_client
>lrwxrwxrwx  1 root root   17 Dec 23 04:35 K12mailman -> ../init.d/mailman
>lrwxrwxrwx  1 root root   13 Aug 24 08:29 K15gpm -> ../init.d/gpm
>lrwxrwxrwx  1 root root   18 Aug 24 08:29 K15svnserve -> ../init.d/svnserve
>lrwxrwxrwx  1 root root   13 Aug 24 08:29 K20nfs -> ../init.d/nfs
>lrwxrwxrwx  1 root root   14 Aug 24 08:29 K24irda -> ../init.d/irda
>lrwxrwxrwx  1 root root   20 Aug 24 08:29 K50netconsole -> ../init.d/netconsole
>lrwxrwxrwx  1 root root   16 Dec 12 12:21 K50vsftpd -> ../init.d/vsftpd
>lrwxrwxrwx  1 root root   20 Aug 24 08:29 K69rpcsvcgssd -> ../init.d/rpcsvcgssd
>lrwxrwxrwx  1 root root   16 Aug 24 08:29 K72autofs -> ../init.d/autofs
>lrwxrwxrwx  1 root root   16 Aug 24 08:29 K73ypbind -> ../init.d/ypbind
>lrwxrwxrwx  1 root root   22 Oct 20 06:42 K74lvm2-monitor -> ../init.d/lvm2-monitor
>lrwxrwxrwx  1 root root   14 Oct 20 06:41 K74nscd -> ../init.d/nscd
>lrwxrwxrwx  1 root root   14 Aug 24 08:29 K74ntpd -> ../init.d/ntpd
>lrwxrwxrwx  1 root root   15 Oct 20 06:42 K75netfs -> ../init.d/netfs
>lrwxrwxrwx  1 root root   19 Aug 24 08:29 K85mdmonitor -> ../init.d/mdmonitor
>lrwxrwxrwx  1 root root   15 Aug 24 08:29 K85mdmpd -> ../init.d/mdmpd
>lrwxrwxrwx  1 root root   17 Aug 24 08:29 K85rpcgssd -> ../init.d/rpcgssd
>lrwxrwxrwx  1 root root   19 Aug 24 08:29 K85rpcidmapd -> ../init.d/rpcidmapd
>lrwxrwxrwx  1 root root   17 Aug 24 08:29 K86nfslock -> ../init.d/nfslock
>lrwxrwxrwx  1 root root   20 Aug 24 08:29 K87irqbalance -> ../init.d/irqbalance
>lrwxrwxrwx  1 root root   20 Aug 24 08:29 K87multipathd -> ../init.d/multipathd
>lrwxrwxrwx  1 root root   16 Aug 24 08:29 K88auditd -> ../init.d/auditd
>lrwxrwxrwx  1 root root   15 Aug 24 08:29 K88pcscd -> ../init.d/pcscd
>lrwxrwxrwx  1 root root   24 Aug 24 08:29 K88wpa_supplicant -> ../init.d/wpa_supplicant
>lrwxrwxrwx  1 root root   14 Aug 24 08:29 K89dund -> ../init.d/dund
>lrwxrwxrwx  1 root root   15 Aug 24 08:29 K89iscsi -> ../init.d/iscsi
>lrwxrwxrwx  1 root root   16 Aug 24 08:29 K89iscsid -> ../init.d/iscsid
>lrwxrwxrwx  1 root root   18 Aug 24 08:29 K89netplugd -> ../init.d/netplugd
>lrwxrwxrwx  1 root root   14 Aug 24 08:29 K89pand -> ../init.d/pand
>lrwxrwxrwx  1 root root   15 Aug 24 08:29 K89rdisc -> ../init.d/rdisc
>lrwxrwxrwx  1 root root   19 Aug 24 08:29 K90bluetooth -> ../init.d/bluetooth
>lrwxrwxrwx  1 root root   19 Aug 24 08:29 K92ip6tables -> ../init.d/ip6tables
>lrwxrwxrwx  1 root root   19 Aug 24 08:29 K95firstboot -> ../init.d/firstboot
>lrwxrwxrwx  1 root root   15 Aug 24 08:29 K95kudzu -> ../init.d/kudzu
>lrwxrwxrwx  1 root root   18 Aug 24 08:29 K99cpuspeed -> ../init.d/cpuspeed
>lrwxrwxrwx  1 root root   25 Aug 24 08:29 K99readahead_later -> ../init.d/readahead_later
>lrwxrwxrwx  1 root root   23 Aug 24 08:29 S00microcode_ctl -> ../init.d/microcode_ctl
>lrwxrwxrwx  1 root root   25 Aug 24 08:29 S04readahead_early -> ../init.d/readahead_early
>lrwxrwxrwx  1 root root   18 Aug 24 08:29 S08iptables -> ../init.d/iptables
>lrwxrwxrwx  1 root root   18 Aug 24 08:29 S08mcstrans -> ../init.d/mcstrans
>lrwxrwxrwx  1 root root   17 Oct 20 06:42 S10network -> ../init.d/network
>lrwxrwxrwx  1 root root   21 Aug 24 08:29 S12restorecond -> ../init.d/restorecond
>lrwxrwxrwx  1 root root   16 Aug 24 08:29 S12syslog -> ../init.d/syslog
>lrwxrwxrwx  1 root root   15 Aug 24 08:29 S13named -> ../init.d/named
>lrwxrwxrwx  1 root root   17 Aug 24 08:29 S13portmap -> ../init.d/portmap
>lrwxrwxrwx  1 root root   20 Oct 20 06:43 S22messagebus -> ../init.d/messagebus
>lrwxrwxrwx  1 root root   15 Aug 24 08:29 S26acpid -> ../init.d/acpid
>lrwxrwxrwx  1 root root   19 Aug 24 08:29 S26haldaemon -> ../init.d/haldaemon
>lrwxrwxrwx  1 root root   14 Aug 24 08:29 S26hidd -> ../init.d/hidd
>lrwxrwxrwx  1 root root   14 Aug 24 08:29 S55sshd -> ../init.d/sshd
>lrwxrwxrwx  1 root root   20 Aug 24 08:29 S56rawdevices -> ../init.d/rawdevices
>lrwxrwxrwx  1 root root   15 Aug 24 08:29 S61clamd -> ../init.d/clamd
>lrwxrwxrwx  1 root root   16 Aug 24 08:29 S64mysqld -> ../init.d/mysqld
>lrwxrwxrwx  1 root root   24 Aug 24 08:29 S78amavisd-milter -> ../init.d/amavisd-milter
>lrwxrwxrwx  1 root root   22 Aug 24 08:29 S78spamassassin -> ../init.d/spamassassin
>lrwxrwxrwx  1 root root   17 Aug 24 08:29 S79amavisd -> ../init.d/amavisd
>lrwxrwxrwx  1 root root   18 Aug 24 08:29 S80sendmail -> ../init.d/sendmail
>lrwxrwxrwx  1 root root   15 Aug 24 08:29 S85httpd -> ../init.d/httpd
>lrwxrwxrwx  1 root root   15 Aug 24 08:29 S90crond -> ../init.d/crond
>lrwxrwxrwx  1 root root   13 Aug 24 08:29 S90xfs -> ../init.d/xfs
>lrwxrwxrwx  1 root root   18 Aug 24 08:29 S92fail2ban -> ../init.d/fail2ban
>lrwxrwxrwx  1 root root   22 Aug 24 08:29 S98avahi-daemon -> ../init.d/avahi-daemon
>lrwxrwxrwx  1 root root   23 Aug 24 08:29 S99lasso8service -> ../init.d/lasso8service
>lrwxrwxrwx  1 root root   11 Oct 20 06:42 S99local -> ../rc.local
>lrwxrwxrwx  1 root root   16 Aug 24 08:29 S99webmin -> ../init.d/webmin
>#############################################################
>This message is sent to you because you are subscribed to
>the mailing list Lasso [hidden email]
>Official list archives available at http://www.lassotalk.com
>To unsubscribe, E-mail to: <[hidden email]>
>Send administrative queries to  <[hidden email]>

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
-- --
Steve Piercy               Web Site Builder              
Soquel, CA
<[hidden email]>                  <http://www.StevePiercy.com/>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Lasso 8.6 not starting automatically at startup

Jussi Hirvi-2
On 2.1.2014 14.11, Steve Piercy - Web Site Builder wrote:
> In your list below, ntpd is the only item that sticks out to me, so I
> would enable it (unless it is enabled somewhere else).
>
>      mv {K74,S26}ntpd

Look at that, I had not noticed that ntpd is off. Though it's not such a
critical service, normally. ANyway, I switched it on now. We'll see at
the next reboot. (I will not do it now because it's 14:24 here and hence
a lot of users.)

I used a different command for the same end:

        chkconfig --level 235 ntpd on

And to check:

        chkconfig --list ntpd

I used to use the "setup" command because it's so easy to use, but I
learned to use chkconfig because I don't have the "setup" command on
every machine any more. On CentOS 5 or 6 you install it by "yum install
setup".

- Jussi
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Lasso 8.6 not starting automatically at startup

Jonathan Guthrie-3
In reply to this post by Jussi Hirvi-2
Hi Jussi,

Have you looked at the following article?
http://www.lassosoft.com/Lasso-86-Fails-to-Start-at-Boot-on-CentOS-5

Thanks
Jono

On Jan 1, 2014, at 3:25 PM, Jussi Hirvi <[hidden email]> wrote:

> Lasso 8.6.0, CentOS 5.10. When the system starts, Lasso tries to start. It takes a long time, probably until some timeout (2 minutes?).
>
> Then when I do
> /etc/init.d/lasso8service status
>
> It says that Lasso is stopped. It starts now normally on command
> /etc/init.d/lasso8service start
>
> Why can it be that it's not starting on system startup? There is nothing on this in the system log (/var/log/messages) or /usr/local/Lasso.../LassoErrors.txt.
>
> - Jussi
> #############################################################
> This message is sent to you because you are subscribed to
> the mailing list Lasso [hidden email]
> Official list archives available at http://www.lassotalk.com
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>

Jono

----------------------------
Jonathan Guthrie
[hidden email]
@iamjono
LassoSoft Inc.
AIM Chatroom: lassochat
IRC/freenode #lasso

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Lasso 8.6 not starting automatically at startup

Jussi Hirvi-2
On 2.1.2014 16.17, Jonathan Guthrie wrote:
> Have you looked at the following article?
> http://www.lassosoft.com/Lasso-86-Fails-to-Start-at-Boot-on-CentOS-5

Thanks Jono, that looks promising, and I will try that if the problem
persists.

- Jussi
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Lasso 8.6 not starting automatically at startup

Jussi Hirvi-2
In reply to this post by Jonathan Guthrie-3
On 2.1.2014 16.17, Jonathan Guthrie wrote:
> Have you looked at the following article?
> http://www.lassosoft.com/Lasso-86-Fails-to-Start-at-Boot-on-CentOS-5

Now I tested this (it being night-time here in the "far East"), and it
works! Now Lasso starts up automatically on system startup. Thanks!

I read elsewhere that the security implications of allowing sudo without
tty are very mild.

- Jussi
#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>
Reply | Threaded
Open this post in threaded view
|

Re: Lasso 8.6 not starting automatically at startup

Eric Knibbe-2
A side note that the need to edit the sudoers file is actually a bug which is fixed in Lasso 8.6.3.
‐‐‐‐‐‐‐‐‐‐✂‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐‐
Eric3
 

On 2014-01-02, at 6:51 PM, Jussi Hirvi wrote:

> On 2.1.2014 16.17, Jonathan Guthrie wrote:
>> Have you looked at the following article?
>> http://www.lassosoft.com/Lasso-86-Fails-to-Start-at-Boot-on-CentOS-5
>
> Now I tested this (it being night-time here in the "far East"), and it works! Now Lasso starts up automatically on system startup. Thanks!
>
> I read elsewhere that the security implications of allowing sudo without tty are very mild.
>
> - Jussi
> #############################################################
> This message is sent to you because you are subscribed to
> the mailing list Lasso [hidden email]
> Official list archives available at http://www.lassotalk.com
> To unsubscribe, E-mail to: <[hidden email]>
> Send administrative queries to  <[hidden email]>

#############################################################
This message is sent to you because you are subscribed to
  the mailing list Lasso [hidden email]
Official list archives available at http://www.lassotalk.com
To unsubscribe, E-mail to: <[hidden email]>
Send administrative queries to  <[hidden email]>