dimad

"received Shutdown Request Via Signal 2" What That?

Recommended Posts

I have a big problem on my debian 7.2 vServer.

 

I start btsync with /etc/init.d/btsync and after 1-2 minutes btsync makes shutdown.

 

here the sync.log

 

 

[20140130 20:37:38.791] total physical memory 536870912 max disk cache 2097152

[20140130 20:37:38.792] Using IP address 127.0.0.2
[20140130 20:37:38.792] Loading config file version 1.2.82
[20140130 20:37:38.807] Loaded folder /var/www/virtual/axx.xx/la
[20140130 20:37:38.820] Loaded folder /var/www/virtual/anexxnus
[20140130 20:38:01.815] Received shutdown request via signal 2
[20140130 20:38:01.843] Shutdown. Saving config sync.dat

 

the config:

 

//!/usr/lib/btsync/btsync-daemon --config
//
// Default instance automatically created by debconf
//
// DO NOT EDIT THIS FILE MANUALLY - SERIOUSLY!!!
//
// THIS FILE WILL BE OVERWRITTEN AT EVERY UPDATE
// OR RECONFIGURATION SO DO NOT EVEN TRY IT
//
// USE dpkg-reconfigure btsync INSTEAD TO MODIFY
// THE CONFIGURATION

// DAEMON_UID=www-data

// DAEMON_GID=www-data
{
"device_name": "gxxr.de",
"storage_path" : "/var/lib/btsync",
"listening_port" : 0,
"check_for_updates" : false,
"use_upnp" : false,
"download_limit" : 0,
"upload_limit" : 0,
"disk_low_priority" : false,
"lan_encrypt_data" : false,
"lan_use_tcp" : false,
"rate_limit_local_peers" : false,
"folder_rescan_interval" : 600,
"webui" :
{
"listen" : "0.0.0.0:9999",
"login" : "xx",
"password" : "xxxx"
}
}

 

can any one help me?

thx

Edited by dimad

Share this post


Link to post
Share on other sites

Strange. According to the Linux Programmers Guide, signal 2 means SIGINT (Terminal Interrupt) - equal to pressing CTRL+C in a foreground application. I think that this is really a support case for the developers. Maybe it's a side effect of the virtualisation layer?

 

Do you have any idea, which hypervisor or virtualisation system is used for your vServer?

Share this post


Link to post
Share on other sites

Its a openVZ Layer.

 

Since 1 month no problems,... today i make only a apt-get update und lost about 3 hours :(

 

now I remove your package and install from this tutorial http://bernaerts.dyndns.org/linux/75-debian/290-debian-server-btsync-permanent-peer and now its run...

 

I'm really wondering, what may be the difference.... The scripts basically do exactly the same thing:

 

start-stop-daemon --start --quiet --chuid $USER --name $NAME --exec $DAEMON -- --config /etc/btsync.conf

 

The only difference is the forking method. The script from http://bernaerts.dyndns.org/linux/75-debian/290-debian-server-btsync-permanent-peer delegates the daemonization to the btsync executable itself. The scripts from my debian packages delegate the daemonization of the btsync executable to the start-stop-daemon routine. I suppose that this may be the reason, since the process has slightly different characteristics.

 

There was a reason for handling it this way (due to some particularity of btsync in the very first versions) but nowadays it could be also implemented in the other way. I would like to test a modified version of my package, but I have no OpenVZ environment with exectly the same characteristics. Would you be available for testing it?

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.