Author Topic: Can anyone explain this log to me?  (Read 1086 times)

ddamron

  • Alumni
  • wants to work for LinuxMCE
  • *
  • Posts: 962
    • View Profile
    • My LinuxMCE User Page
Can anyone explain this log to me?
« on: May 03, 2007, 07:49:46 pm »
== ATTEMPT FRESH START ==
1   05/03/07 10:10:17   /usr/pluto/bin/Spawn_Device.sh 21 (spawning-device)   26924 Dev: 21; Already Running list:
== FRESH START ==
1   05/03/07 10:10:17   /usr/pluto/bin/Spawn_Device.sh 21 (spawning-device)   device: 21 ip: localhost cmd_line: HAL
0   05/03/07 10:10:17   21 (spawning-device)   Entering 21
========== NEW LOG SECTION ==========
1   05/03/07 10:10:17   21 (spawning-device)   Starting... 1
1   05/03/07 10:10:17   21 (spawning-device)   Found ./HAL
05   05/03/07 10:10:40.825      Got a reload command from 0  <0xb618aba0>
05   05/03/07 10:10:41.383      ############ QUIT ++++++++++++++ <0xb798dba0>
05   05/03/07 10:10:42.184      void ClientSocket::Disconnect() on this socket: 0x8070170 (m_Socket: 6) <0xb79a66b0>
Return code: 2
2   05/03/07 10:10:42   21 (spawning-device)   Device requests restart... count=1/50 dev=21
Thu May  3 10:10:42 MDT 2007 Restart
========== NEW LOG SECTION ==========
1   05/03/07 10:10:50   21 (spawning-device)   Starting... 1
1   05/03/07 10:10:50   21 (spawning-device)   Found ./HAL
05   05/03/07 10:23:47.966      Got a reload command from 0  <0xb61c1ba0>
05   05/03/07 10:23:48.486      ############ QUIT ++++++++++++++ <0xb79c4ba0>
05   05/03/07 10:23:48.952      void ClientSocket::Disconnect() on this socket: 0x8070170 (m_Socket: 6) <0xb79dd6b0>
Return code: 2
2   05/03/07 10:23:48   21 (spawning-device)   Device requests restart... count=1/50 dev=21
Thu May  3 10:23:48 MDT 2007 Restart
========== NEW LOG SECTION ==========
1   05/03/07 10:23:57   21 (spawning-device)   Starting... 1
1   05/03/07 10:23:57   21 (spawning-device)   Found ./HAL
05   05/03/07 10:27:51.120      Got a reload command from 0  <0xb6237ba0>
05   05/03/07 10:27:51.618      ############ QUIT ++++++++++++++ <0xb7a3aba0>
05   05/03/07 10:27:52.115      void ClientSocket::Disconnect() on this socket: 0x8070170 (m_Socket: 6) <0xb7a536b0>
Return code: 2
2   05/03/07 10:27:52   21 (spawning-device)   Device requests restart... count=1/50 dev=21
Thu May  3 10:27:52 MDT 2007 Restart
========== NEW LOG SECTION ==========
1   05/03/07 10:28:00   21 (spawning-device)   Starting... 1
1   05/03/07 10:28:00   21 (spawning-device)   Found ./HAL
05   05/03/07 10:33:22.719      Got a reload command from 0  <0xb6193ba0>
05   05/03/07 10:33:23.171      ############ QUIT ++++++++++++++ <0xb7996ba0>
05   05/03/07 10:33:23.516      void ClientSocket::Disconnect() on this socket: 0x8070170 (m_Socket: 6) <0xb79af6b0>
Return code: 2
2   05/03/07 10:33:23   21 (spawning-device)   Device requests restart... count=1/50 dev=21
Thu May  3 10:33:23 MDT 2007 Restart
========== NEW LOG SECTION ==========
1   05/03/07 10:33:31   21 (spawning-device)   Starting... 1
1   05/03/07 10:33:31   21 (spawning-device)   Found ./HAL
05   05/03/07 10:36:25.965      Got a reload command from 0  <0xb621dba0>
05   05/03/07 10:36:26.552      ############ QUIT ++++++++++++++ <0xb7a20ba0>
05   05/03/07 10:36:27.437      void ClientSocket::Disconnect() on this socket: 0x8070170 (m_Socket: 6) <0xb7a396b0>
Return code: 2
2   05/03/07 10:36:27   21 (spawning-device)   Device requests restart... count=1/50 dev=21
Thu May  3 10:36:27 MDT 2007 Restart
========== NEW LOG SECTION ==========
1   05/03/07 10:36:35   21 (spawning-device)   Starting... 1
1   05/03/07 10:36:35   21 (spawning-device)   Found ./HAL
I had the problem HAL failed to initialize.
when I did a sudo /etc/init.d/dbus restart, all but avahi-daemon was ok.
I used synaptic to reinstall avahi-daemon, and now dbus restart is all ok.
however, I get this on my media director (on the core)



05   05/03/07 10:56:29.011      Got a reload command from 0  <0xb618cba0>
05   05/03/07 10:56:29.427      ############ QUIT ++++++++++++++ <0xb798fba0>
05   05/03/07 10:56:29.571      void ClientSocket::Disconnect() on this socket: 0x8070170 (m_Socket: 6) <0xb79a86b0>
Return code: 2
2   05/03/07 10:56:29   21 (spawning-device)   Device requests restart... count=1/50 dev=21
Thu May  3 10:56:29 MDT 2007 Restart
========== NEW LOG SECTION ==========
1   05/03/07 10:56:37   21 (spawning-device)   Starting... 1
1   05/03/07 10:56:37   21 (spawning-device)   Found ./HAL
05   05/03/07 11:00:28.586      Socket::ReceiveData 0x8070170 failed, bytes left 0 start: 0 1: 0 1b: 0 2: 0 2b: 0 m_Socket: 6 Command_Impl1 Dev #21 <0xb615eba0>
05   05/03/07 11:00:28.586      Socket::ReceiveString2 ReceiveData failed m_Socket: -1 Command_Impl1 Dev #21 <0xb615eba0>
01   05/03/07 11:00:28.586      Receive string failed in HandleRequestSocket 18:ReceiveData failed Command_Impl1 Dev #21 <0xb615eba0>
05   05/03/07 11:00:28.586      Dumping 1 locks <0xb615eba0>
05   05/03/07 11:00:28.586      finished check for exceptions <0xb615eba0>
05   05/03/07 11:00:28.586      OL: (0x807029c) (>82) MessageQueue Command_Impl.cpp l:786 time: 5:00:00p (1178211628 s) thread: 3063282592 Rel: Y Got: Y <0xb615eba0>
05   05/03/07 11:00:28.742      ############ QUIT ++++++++++++++ <0xb7961ba0>
Return code: 2
2   05/03/07 11:00:28   21 (spawning-device)   Device requests restart... count=1/50 dev=21
Thu May  3 11:00:29 MDT 2007 Restart
========== NEW LOG SECTION ==========
1   05/03/07 11:00:37   21 (spawning-device)   Starting... 1
1   05/03/07 11:00:37   21 (spawning-device)   Found ./HAL
05   05/03/07 11:05:21.346      Got a reload command from 0  <0xb61b5ba0>
05   05/03/07 11:05:21.886      ############ QUIT ++++++++++++++ <0xb79b8ba0>
05   05/03/07 11:05:22.564      void ClientSocket::Disconnect() on this socket: 0x8070170 (m_Socket: 6) <0xb79d16b0>
Return code: 2
2   05/03/07 11:05:22   21 (spawning-device)   Device requests restart... count=1/50 dev=21
Thu May  3 11:05:22 MDT 2007 Restart
========== NEW LOG SECTION ==========
1   05/03/07 11:05:30   21 (spawning-device)   Starting... 1
1   05/03/07 11:05:30   21 (spawning-device)   Found ./HAL
05   05/03/07 11:06:41.253      Got a reload command from 0  <0xb616bba0>
05   05/03/07 11:06:41.593      ############ QUIT ++++++++++++++ <0xb796eba0>
05   05/03/07 11:06:42.047      void ClientSocket::Disconnect() on this socket: 0x8070170 (m_Socket: 6) <0xb79876b0>
Return code: 2
2   05/03/07 11:06:42   21 (spawning-device)   Device requests restart... count=1/50 dev=21
Thu May  3 11:06:42 MDT 2007 Restart
========== NEW LOG SECTION ==========
1   05/03/07 11:06:50   21 (spawning-device)   Starting... 1
1   05/03/07 11:06:50   21 (spawning-device)   Found ./HAL
Return code: 1
3   05/03/07 11:09:42   21 (spawning-device)   Device died... count=1/50 dev=21
Thu May  3 11:09:42 MDT 2007 died
== ATTEMPT FRESH START ==
1   05/03/07 11:11:57   /usr/pluto/bin/Spawn_Device.sh 21 (spawning-device)   7559 Dev: 21; Already Running list:
== FRESH START ==
1   05/03/07 11:11:57   /usr/pluto/bin/Spawn_Device.sh 21 (spawning-device)   device: 21 ip: localhost cmd_line: HAL
0   05/03/07 11:11:57   21 (spawning-device)   Entering 21
========== NEW LOG SECTION ==========
1   05/03/07 11:11:57   21 (spawning-device)   Starting... 1
1   05/03/07 11:11:57   21 (spawning-device)   Found ./HAL
05   05/03/07 11:21:14.745      Got a reload command from 0  <0xb615fba0>
The only intuitive interface is the nipple.  After that it's all learned.
My other computer is your windows box.
I'm out of my mind.  Back in 5 minutes.
Q:  What's Red and smells like blue paint?

A:  Red Paint.

ddamron

  • Alumni
  • wants to work for LinuxMCE
  • *
  • Posts: 962
    • View Profile
    • My LinuxMCE User Page
Re: Can anyone explain this log to me?
« Reply #1 on: May 03, 2007, 07:55:44 pm »
 I am still getting the unable to init hal upon startup...
and here's my daemon log:

May  3 11:34:53 dcerouter named[4413]: starting BIND 9.3.2 -u bind
May  3 11:34:53 dcerouter named[4413]: found 2 CPUs, using 2 worker threads
May  3 11:34:53 dcerouter named[4413]: loading configuration from '/etc/bind/named.conf'
May  3 11:34:53 dcerouter named[4413]: listening on IPv4 interface lo, 127.0.0.1#53
May  3 11:34:53 dcerouter named[4413]: listening on IPv4 interface eth0, 192.168.2.81#53
May  3 11:34:53 dcerouter named[4413]: listening on IPv4 interface eth1, 192.168.80.1#53
May  3 11:34:53 dcerouter named[4413]: command channel listening on 127.0.0.1#953
May  3 11:34:53 dcerouter named[4413]: command channel listening on ::1#953
May  3 11:34:53 dcerouter named[4413]: zone 0.in-addr.arpa/IN: loaded serial 1
May  3 11:34:53 dcerouter named[4413]: zone 127.in-addr.arpa/IN: loaded serial 1
May  3 11:34:53 dcerouter named[4413]: zone 255.in-addr.arpa/IN: loaded serial 1
May  3 11:34:53 dcerouter named[4413]: zone activate.plutohome.com/IN: loaded serial 45
May  3 11:34:53 dcerouter named[4413]: zone localhost/IN: loaded serial 1
May  3 11:34:53 dcerouter named[4413]: running
May  3 11:34:53 dcerouter ypserv[4432]: refused connect from 192.168.2.81:32771 to procedure ypproc_domain_nonack (pluto,;0)
May  3 11:34:55 dcerouter kernel: [17179600.372000] eth0: no IPv6 routers present
May  3 11:34:59 dcerouter gconfd (dan-4504): starting (version 2.16.0), pid 4504 user 'dan'
May  3 11:34:59 dcerouter gconfd (dan-4504): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
May  3 11:34:59 dcerouter gconfd (dan-4504): Resolved address "xml:readwrite:/home/dan/.gconf" to a writable configuration source at position 1
May  3 11:34:59 dcerouter gconfd (dan-4504): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
May  3 11:34:59 dcerouter gconfd (dan-4504): Resolved address "xml:readonly:/var/lib/gconf/debian.defaults" to a read-only configuration source at position 3
May  3 11:34:59 dcerouter gconfd (dan-4504): Resolved address "xml:readonly:/var/lib/gconf/defaults" to a read-only configuration source at position 4
May  3 11:35:02 dcerouter gconfd (dan-4504): Resolved address "xml:readwrite:/home/dan/.gconf" to a writable configuration source at position 0
May  3 11:35:03 dcerouter gnome-power-manager: (dan) Critical error: This program cannot start until you start the dbus system service. It is <b>strongly recommended</b> you reboot your computer after starting this service.
May  3 11:35:47 dcerouter ypbind[4445]: broadcast: RPC: Timed out.
May  3 11:36:41 dcerouter ypbind[4445]: broadcast: RPC: Timed out.
The only intuitive interface is the nipple.  After that it's all learned.
My other computer is your windows box.
I'm out of my mind.  Back in 5 minutes.
Q:  What's Red and smells like blue paint?

A:  Red Paint.

sharlee_angelo

  • Guru
  • ****
  • Posts: 316
    • View Profile
Re: Can anyone explain this log to me?
« Reply #2 on: May 04, 2007, 02:37:17 pm »
you didn't said what problem you have.
Read the F****** Logs!!!

ddamron

  • Alumni
  • wants to work for LinuxMCE
  • *
  • Posts: 962
    • View Profile
    • My LinuxMCE User Page
Re: Can anyone explain this log to me?
« Reply #3 on: May 04, 2007, 08:07:34 pm »
HAL died..
The only intuitive interface is the nipple.  After that it's all learned.
My other computer is your windows box.
I'm out of my mind.  Back in 5 minutes.
Q:  What's Red and smells like blue paint?

A:  Red Paint.