bonescript.socket error

[JacquesBBB]

after struggling with opkg update and upgrade

(see http://beagleboard.org/Community/Forums?utm_expid=6702460-6&utm_referrer=http%3A%2F%2Fbeagleboard.org%2FProducts%2FBeagleBone)

I remain with this  bonescript.socket  error :

root@beaglebone:~# opkg upgrade

Configuring bonescript.

Job for bonescript.socket failed. See 'systemctl status bonescript.socket' and 'journalctl -xn' for details.

Collected errors:

 * pkg_run_script: package "bonescript" postinst script returned status 1.

 * opkg_configure: bonescript.postinst returned 1.

with the outputs

root@beaglebone:~# systemctl status bonescript.socket

bonescript.socket

 Loaded: loaded (/lib/systemd/system/bonescript.socket; enabled)

 Active: inactive (dead)

 CGroup: name=systemd:/system/bonescript.socket

root@beaglebone:~# journalctl -xn

-- Logs begin at Sat 2000-01-01 00:00:02 UTC, end at Sat 2000-01-01 02:19:11 UTC. --

Jan 01 02:19:11 beaglebone systemd[1]: Stopping Load Kernel Modules...

Jan 01 02:19:11 beaglebone systemd[1]: Unmounted /tmp.

Jan 01 02:19:11 beaglebone systemd[1]: Starting Unmount All Filesystems.

Jan 01 02:19:11 beaglebone systemd[1]: Starting Save Random Seed...

Jan 01 02:19:11 beaglebone systemd[1]: Started Save Random Seed.

Jan 01 02:19:11 beaglebone systemd[1]: Started Update UTMP about System Shutdown.

Jan 01 02:19:11 beaglebone systemd[1]: Shutting down.

Jan 01 02:19:11 beaglebone systemd-cgroups-agent[1383]: Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused

Jan 01 02:19:11 beaglebone systemd-cgroups-agent[1384]: Failed to get D-Bus connection: Failed to connect to socket /org/freedesktop/systemd1/private: Connection refused

Jan 01 02:19:11 beaglebone systemd-journal[87]: Journal stopped

what is the meaning of this error ? 

Thanks 

Jacques

[Dave M]

I have the same problem, though a slightly different error.  The first time I ran it, I got this:

root@beaglebone:~# opkg install bonescript
Package bonescript (1.0-r21.4) installed in root is up to date.

Configuring bonescript.
Job for bonescript.socket failed. See 'systemctl status bonescript.socket' and 'journalctl -xn' for details.
Collected errors:
 * pkg_run_script: package "bonescript" postinst script returned status 1.
 * opkg_configure: bonescript.postinst returned 1.

root@beaglebone:~#

root@beaglebone:~# systemctl status bonescript.socket
bonescript.socket
          Loaded: loaded (/lib/systemd/system/bonescript.socket; enabled)
          Active: inactive (dead)
          CGroup: name=systemd:/system/bonescript.socket

Jan 01 04:00:01 beaglebone systemd[1]: Failed to listen on bonescript.socket.
root@beaglebone:~# journalctl -xn
WARNING: terminal is not fully functional
-- Logs begin at Sat 2000-01-01 00:00:03 UTC, end at Sat 2000-01-01 04:00:26 UTC. --
Jan 01 04:00:01 beaglebone systemd[1]: Started Bonescript autorun.
Jan 01 04:00:01 beaglebone systemd[1]: Starting Bonescript server...
Jan 01 04:00:01 beaglebone systemd[1]: Started Bonescript server.
Jan 01 04:00:01 beaglebone systemd[1]: Starting bonescript.socket.
Jan 01 04:00:01 beaglebone systemd[1]: Socket service bonescript.service already active, refusing.
Jan 01 04:00:01 beaglebone systemd[1]: Failed to listen on bonescript.socket.
Jan 01 04:00:04 beaglebone bonescript[611]: [35B blob data]
Jan 01 04:00:06 beaglebone kernel: [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 2 to 2
Jan 01 04:00:16 beaglebone kernel: [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 2 to 2
Jan 01 04:00:26 beaglebone kernel: [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 2 to 2

When I saw "connection refused", I then noticed that I still had Cloud9 open, so I closed it and ran it again.  Basically, this didn't help, either.

root@beaglebone:~# opkg install bonescript
Package bonescript (1.0-r21.4) installed in root is up to date.

Configuring bonescript.
Job for bonescript.socket failed. See 'systemctl status bonescript.socket' and 'journalctl -xn' for details.
Collected errors:
 * pkg_run_script: package "bonescript" postinst script returned status 1.
 * opkg_configure: bonescript.postinst returned 1.

root@beaglebone:~# systemctl status bonescript.socket
bonescript.socket
          Loaded: loaded (/lib/systemd/system/bonescript.socket; enabled)
          Active: inactive (dead)
          CGroup: name=systemd:/system/bonescript.socket

Jan 01 04:00:01 beaglebone systemd[1]: Failed to listen on bonescript.socket.
Jan 01 04:01:21 beaglebone systemd[1]: Starting bonescript.socket.
Jan 01 04:01:21 beaglebone systemd[1]: Failed to listen on bonescript.socket.
root@beaglebone:~# journalctl -xn
WARNING: terminal is not fully functional
-- Logs begin at Sat 2000-01-01 00:00:03 UTC, end at Sat 2000-01-01 04:01:27 UTC. --
Jan 01 04:00:57 beaglebone kernel: [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 2 to 2
Jan 01 04:01:07 beaglebone kernel: [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 2 to 2
Jan 01 04:01:17 beaglebone kernel: [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 2 to 2
Jan 01 04:01:21 beaglebone systemd[1]: Reloading.
Jan 01 04:01:21 beaglebone systemd[1]: Started Bonescript autorun.
Jan 01 04:01:21 beaglebone systemd[1]: Started Bonescript server.
Jan 01 04:01:21 beaglebone systemd[1]: Starting bonescript.socket.
Jan 01 04:01:21 beaglebone systemd[1]: Socket service bonescript.service already active, refusing.
Jan 01 04:01:21 beaglebone systemd[1]: Failed to listen on bonescript.socket.
Jan 01 04:01:27 beaglebone kernel: [drm:output_poll_execute], [CONNECTOR:5:HDMI-A-1] status updated from 2 to 2
root@beaglebone:~#

Does anyone know what else to do?  Cloud9 still seems to be working after a reboot, so I don't know what has actually failed here...

[gary....@gmail.com]

I am also seeing this problem on a new BBB out of the box, first update/upgrade. I've found very little relevant information on the web to help debug. One suggestion I found was to simply go to the file mentioned and comment out lines to make the problem go away. Didn't say which lines and doesn't sound like a solution anyway. But could help with debugging.

[techt...@gmail.com]

I was getting a similar error when I was trying to install "opkg install python-compiler". If you try to run "systemctl start bonescript.socket" - it will fail as well. So it was NOT about the service not running. If you open this file (bonescript.socket) you will notice it is listening on Port 80. On my BBB - the node.js server was running - run "ps -ax" to find it. If you kill the server and then start the bonescript.socket - you should be able to get past this problem. In simple words - bonescript.socket does not run because Port 80 was already being used. 

[jue...@gmail.com]

Am Samstag, 6. Juli 2013 20:00:52 UTC+2 schrieb Ashu Joshi:

I was getting a similar error when I was trying to install "opkg install python-compiler". If you try to run "systemctl start bonescript.socket" - it will fail as well. So it was NOT about the service not running. If you open this file (bonescript.socket) you will notice it is listening on Port 80. On my BBB - the node.js server was running - run "ps -ax" to find it. If you kill the server and then start the bonescript.socket - you should be able to get past this problem. In simple words - bonescript.socket does not run because Port 80 was already being used. 

How can I kill all processes accessing port 80? I tried already:

systemctl disable cloud9.service                  
systemctl disable gateone.service                 
systemctl disable bonescript.service              
systemctl disable bonescript-autorun.service      
systemctl disable avahi-daemon.service            
systemctl disable gdm.service

and 

root@beaglebone1:/home/root(6)# systemctl stop cloud9.service   
root@beaglebone1:/home/root(7)# systemctl stop gateone.service   
root@beaglebone1:/home/root(8)# systemctl stop bonescript.service    
root@beaglebone1:/home/root(9)# systemctl stop bonescript-autorun.service 
root@beaglebone1:/home/root(10)# systemctl stop avahi-daemon.service       
Warning: Stopping avahi-daemon.service, but it can still be activated by:
  avahi-daemon.socket


But I still get "bonescript.socket failed":

root@beaglebone1:/home/root(11)# opkg install ethtool
Package ethtool (3.5-r0.1) installed in root is up to date.

Configuring bonescript.
Job for bonescript.socket failed. See 'systemctl status bonescript.socket' and 'journalctl -xn' for details.
Collected errors:
 * pkg_run_script: package "bonescript" postinst script returned status 1.
 * opkg_configure: bonescript.postinst returned 1.

root@beaglebone1:/home/root(12)# systemctl status bonescript.socket

bonescript.socket
          Loaded: loaded (/lib/systemd/system/bonescript.socket; enabled)
          Active: inactive (dead)
          CGroup: name=systemd:/system/bonescript.socket

Oct 14 14:07:41 beaglebone1 systemd[1]: Starting bonescript.socket.
Oct 14 14:07:41 beaglebone1 systemd[1]: Failed to listen on bonescript.socket.
Oct 14 14:09:13 beaglebone1 systemd[1]: Starting bonescript.socket.
Oct 14 14:09:13 beaglebone1 systemd[1]: Failed to listen on bonescript.socket.
Oct 14 14:10:41 beaglebone1 systemd[1]: Starting bonescript.socket.
Oct 14 14:10:41 beaglebone1 systemd[1]: Failed to listen on bonescript.socket.
Oct 14 15:53:28 beaglebone1 systemd[1]: Starting bonescript.socket.
Oct 14 15:53:28 beaglebone1 systemd[1]: Failed to listen on bonescript.socket.
Oct 14 16:02:50 beaglebone1 systemd[1]: Starting bonescript.socket.
Oct 14 16:02:50 beaglebone1 systemd[1]: Failed to listen on bonescript.socket.


root@beaglebone1:/home/root(13)# journalctl -xn
-- Logs begin at Sat 2013-10-12 23:56:23 CEST, end at Mon 2013-10-14 16:02:53 CEST. --
Oct 14 16:02:12 beaglebone1 systemd[1]: Stopped Avahi mDNS/DNS-SD Stack.
Oct 14 16:02:49 beaglebone1 systemd[1]: Reloading.
Oct 14 16:02:50 beaglebone1 systemd[1]: Starting Bonescript autorun...
Oct 14 16:02:50 beaglebone1 systemd[1]: Started Bonescript autorun.
Oct 14 16:02:50 beaglebone1 systemd[1]: Starting Bonescript server...
Oct 14 16:02:50 beaglebone1 systemd[1]: Started Bonescript server.
Oct 14 16:02:50 beaglebone1 systemd[1]: Starting bonescript.socket.
Oct 14 16:02:50 beaglebone1 systemd[1]: Socket service bonescript.service already active, refusing.


root@beaglebone1:/home/root(14)# systemctl stop bonescript.service  
root@beaglebone1:/home/root(15)# systemctl stop bonescript.socket   


Oct 14 16:02:50 beaglebone1 systemd[1]: Failed to listen on bonescript.socket.
Oct 14 16:02:53 beaglebone1 bonescript[1848]: [35B blob data]

root@beaglebone1:/home/root(16)# opkg install ethtool
Package ethtool (3.5-r0.1) installed in root is up to date.

Configuring bonescript.
Job for bonescript.socket failed. See 'systemctl status bonescript.socket' and 'journalctl -xn' for details.
Collected errors:
 * pkg_run_script: package "bonescript" postinst script returned status 1.
 * opkg_configure: bonescript.postinst returned 1.

root@beaglebone1:/home/root(17)# systemctl stop bonescript-autorun.service

root@beaglebone1:/home/root(18)# opkg install ethtool
Package ethtool (3.5-r0.1) installed in root is up to date.

[hamme...@gmail.com]

Had the same problem bonescript socket error after running opkg install bonescript

To solve that just do what they say.

1. kill node.js

2. start bonescript.socket again and your good to go.

root@beaglebone:~# opkg install bonescript

Package bonescript (1.0-r21.5) installed in root is up to date.

Configuring bonescript.

Job for bonescript.socket failed. See 'systemctl status bonescript.socket' and 'journalctl -xn' for details.

Collected errors:

 * pkg_run_script: package "bonescript" postinst script returned status 1.

 * opkg_configure: bonescript.postinst returned 1.

root@beaglebone:~# ps -ef | grep -i js$

root       125     1  0 Nov16 ?        00:00:01 /usr/bin/node autorun.js

root       679     1  1 Nov16 ?        00:00:13 /usr/bin/node server.js

root@beaglebone:~# kill -9 679

root@beaglebone:~# systemctl start bonescript.socket

root@beaglebone:~# systemctl status bonescript.socket

bonescript.socket

         Loaded: loaded (/lib/systemd/system/bonescript.socket; enabled)

         Active: active (running) since Sun 2013-11-17 00:06:58 UTC; 23s ago

         CGroup: name=systemd:/system/bonescript.socket

[Orest Lenczyk]

i have similar issue

status command:

root@beaglebone:~/skrypty# systemctl status bonescript.socket

bonescript.socket

          Loaded: loaded (/lib/systemd/system/bonescript.socket; enabled)

          Active: inactive (dead)

          CGroup: name=systemd:/system/bonescript.socket

Nov 13 12:02:31 beaglebone systemd[1]: Starting bonescript.socket.

Nov 13 12:02:31 beaglebone systemd[1]: Failed to listen on bonescript.socket.

Nov 13 12:04:15 beaglebone systemd[1]: Starting bonescript.socket.

Nov 13 12:04:15 beaglebone systemd[1]: Failed to listen on bonescript.socket.

Nov 13 12:04:56 beaglebone systemd[1]: Closed bonescript.socket.

Nov 13 12:05:11 beaglebone systemd[1]: Starting bonescript.socket.

Nov 13 12:05:11 beaglebone systemd[1]: Failed to listen on bonescript.socket.

as you can see, after closing and starting there is still "Failed to listen on bonescript.socket". journalctl -xn is telling: Socket service bonescript.service already active, refusing.It is confusing