Startup file doesn't work

I give another workaround at the following adress:
http://debuntu.org/2006/04/03/14-how-to-dapper-and-starting-mldonkey-mlnet-file-s-not-owned-by-user-113-or-group-1001-var-run-reown-it-first
This workaround is more into the breezy/debian way

The blog system running on debuntu has changed, please go to
http://debuntu.org/2006/04/03/13-how-to-dapper-and-starting-mldonkey-mlnet-file-s-not-owned-by-user-113-or-group-1001-var-run-reown-it-first
instead.

Thanks for your bug report. What error do you get if you leave this line uncommented?

Before any modification, if you tyed to run mldonkey you got the following
error message and it didn't startup:

Starting MLDonkey: mlnet file[s] not owned by user 113 or group 1001:
/var/run — reown it first

On 7/25/06, Jérémie Corbier <email address hidden> wrote:
>
> Thanks for your bug report. What error do you get if you leave this line
> uncommented?
>
> ** Changed in: mldonkey (Ubuntu)
> Assignee: MOTU => Jérémie Corbier
> Status: Confirmed => Needs Info
>
> ** Changed in: mldonkey (Ubuntu)
> Importance: Medium => Low
>
> --
> Startup file doesn't work
> https://launchpad.net/bugs/35914
>

Is this still issue for Dapper/Edgy ?

yes, still ist does not work out if the box.

Yeah, still on mldonkey-server 2.8.1-1 too.

Okay I got this working!

The patch that chantra gave did not help here. Neither did the original suggestion in the bug description of commenting out one of the WRAPPER_OPTIONS= lines.

I think this fix will probably work for the following bugs, which are likely caused by the same error:

65743
70177

What I found was that when the /etc/init.d/mldonkey-server script runs and tries to start mlnet, it executes an install command with the invalid -f option. It seems that the author intended to create a blank $PIDFILE (/var/run/mlnet.pid) with explicit user, group, and permissions. But the author botched that. For one, the install command does not take a -f option. Instead it should have a source and destination file. So for another, $PIDFILE I would assume is the intended destination file but no source file is given.

Looking further, I learned that the following line calls start-stop-daemon to actually start or kill the mlnet server process. Since start-stop-daemon is passed the --pidfile $PIDFILE argument, it will create the file if it does not exist and populate it with the process id for the mlnet process. If the /var/log/mlnet.pid file already exists, then it will error out and indicate that mldonkey-server (mlnet) is already running.

SO... The answer is to simply comment out the install command line, and it starts to work fine.

This error causes installing (or uninstalling) the mldonkey-server package with APT or Synaptic (or whatever) to fail as well, because the script is called to stop and/or start the mlnet daemon as part of the (un|re)installation.

I don't know how to create patch files, even though it's probably easy. So instead I will just attach my modified /etc/init.d/mldonkey-server script. You can back up or rename your existing one and try mine out in it's place to see if it fixes you as well.

PEACE!

Tim LePes

Okay I got this working!

The patch that chantra gave did not help here. Neither did the original suggestion in the bug description of commenting out one of the WRAPPER_OPTIONS= lines.

I think this fix will probably work for the following bugs, which are likely caused by the same error:

65743
70177

What I found was that when the /etc/init.d/mldonkey-server script runs and tries to start mlnet, it executes an install command with the invalid -f option. It seems that the author intended to create a blank $PIDFILE (/var/run/mlnet.pid) with explicit user, group, and permissions. But the author botched that. For one, the install command does not take a -f option. Instead it should have a source and destination file. So for another, $PIDFILE I would assume is the intended destination file but no source file is given.

Looking further, I learned that the following line calls start-stop-daemon to actually start or kill the mlnet server process. Since start-stop-daemon is passed the --pidfile $PIDFILE argument, it will create the file if it does not exist and populate it with the process id for the mlnet process. If the /var/log/mlnet.pid file already exists, then it will error out and indicate that mldonkey-server (mlnet) is already running.

SO... The answer is to simply comment out the install command line, and it starts to work fine.

This error causes installing (or uninstalling) the mldonkey-server package with APT or Synaptic (or whatever) to fail as well, because the script is called to stop and/or start the mlnet daemon as part of the (un|re)installation.

I don't know how to create patch files, even though it's probably easy. So instead I will just attach my modified /etc/init.d/mldonkey-server script. You can back up or rename your existing one and try mine out in it's place to see if it fixes you as well.

PEACE!

Tim LePes

I have mldonkey 2.8.1-1, and it does not start on the boot process (it's configured to do so), but if I manually start it once logged in, it works. I don't know why that's happen.

The log for the failed start of mldonkey on boot is this:

Nov 29 07:31:42 wasabi mldonkey_server: Set niceness of the process: 5
Nov 29 07:31:42 wasabi mldonkey_server: Set uid/gid of the process (110, 1001)
Nov 29 07:31:42 wasabi mldonkey_server: Set umask of the process: 18

It appear to do begin normally, but it stops there and does not start. The log when I start it once I am logged in is this:

Nov 29 09:30:36 wasabi mldonkey_server: Set niceness of the process: 5
Nov 29 09:30:36 wasabi mldonkey_server: Set uid/gid of the process (110, 1001)
Nov 29 09:30:36 wasabi mldonkey_server: Set umask of the process: 18
Nov 29 09:30:36 wasabi mldonkey_server: Chdir to home dir: /home/miltondp
Nov 29 09:30:36 wasabi mldonkey_server: Fork the process
Nov 29 09:30:36 wasabi mldonkey_server: Reset the group leader
Nov 29 09:30:36 wasabi mldonkey_server: Fork a second time the process
Nov 29 09:30:36 wasabi mldonkey_server: Close standard IO
Nov 29 09:30:36 wasabi mldonkey_server: Process is running in the background
Nov 29 09:30:36 wasabi mldonkey_server: Writing PID (10505) to pidfile: /var/run/mldonkey/mlnet.pid
Nov 29 09:30:36 wasabi mldonkey_server: Launching MLnet process
Nov 29 09:30:36 wasabi mldonkey_server: Launching MLnet stderr logger
Nov 29 09:30:36 wasabi mldonkey_server: Launching MLnet stdout logger
Nov 29 09:30:36 wasabi mlnet_error: 2006/11/29 09:30:36 Loading language resource /var/lib/mldonkey/mlnet_strings.es_AR.UTF-8
Nov 29 09:30:36 wasabi mlnet_error: 2006/11/29 09:30:36 [DNS] Resolving [www.mldonkey.net] ...

... and it's now running normally.

This problem exists in the package included in ubuntu feisty (current development version).

Hm.. it could be caused by this:

Exception: bind failed: Address already in use at port 6881
This is normally caused by another application currently using this port.
Close that application and restart MLDonkey, exiting...

Since I have a bittorrent client running now :P

That's not the problem according to the log. I neither have a client nor a bittorrent server. If I start mldonkey once the system is up, it works.

OK, I think I've had some success starting mldonkey; here's what I had to do:

1- The shell for the user 'mldonkey' is set to /bin/false; needed change it to /bin/sh;
2- The file users.ini in /var/lib/mldonkey is broken. Here's a sample:

 users2 = [

  { user_name = admin

     user_pass = "XXX...XXX"

     user_mail = ""

};]

(replace XXX...XXX with your password hash)

Next problem was how to start the GUI. You run the command 'mlgui' and it complains about bad authorization and asks you to press the "settings button" which was nowhere to be found. Well, guess where it is... it's only available as a menu item in the popup menu of the systray icon! :|

Anyway, hope this helps..

Thank you very much Gustavo, but my problem is that mldonkey is not automatically started on start up, but it run when I execute it from a console, when the boot process has ended. I don't know why it happens.

Sorry, for the spam, just a small errata: changing the mldonkey user shell from /bin/false to /bin/sh is not needed after all, so nevermind that. It was only useful temporarily in order to debug what was wrong...

Sorry Milton. In fact I might have the same problem as you, since I have not yet rebooted the PC after installing mldonkey... :P

OK, just reporting that last time I tried installing this package from scratch (after --purge), it just worked. It was a month ago, in Ubuntu gutsy. So this bug is likely already fixed.

This is fixed in Feisty.

Marking as fixed according to previous comments.

I still have this problem. It shows no error, but the core doesn't start.
This started after I did an apt-get upgrade.

can anyone help ?

Maybe you need to apt-get remove --purge mldonkey, and then reinstall it. Note however that you lose your configuration files, though probably you will keep current downloads at the same progress level.