aMule Forum
English => en_Linux => Topic started by: x0rsw1tch on January 05, 2010, 01:07:35 PM
-
I cant figure this out for the life of me... For some reason when I start amule with the init script, amuleweb doesnt work - I get the "no password specified, login disabled" message. But if I launch aMule from the GUI, it works fine.
:headexpode:
heres the init script....
# Include amule defaults if available
if [ -f /etc/default/amule ] ; then
. /etc/default/amule
fi
if [ "$RUNAMULE" != "yes" ] ; then
echo "Amule not to be started. Edit /etc/default/amule first."
exit 1
fi
set -e
case "$1" in
start)
echo -n "Starting $DESC: "
su $USER -c "$DAEMON -f"
while ! netstat -l -n -p -t | grep -q amuled ; do sleep 1 ; done
su $USER -c "$WEB --quiet &"
echo "$NAME."
;;
stop)
echo -n "Stopping $DESC: "
killall --quiet --ignore-case $WEB
killall --quiet --ignore-case $DAEMON
echo "$NAME."
;;
restart|force-reload)
echo -n "Restarting $DESC: "
killall --quiet --ignore-case $WEB
killall --quiet --ignore-case $DAEMON
sleep 1
su $USER -c "$DAEMON -f"
while ! netstat -l -n -p -t | grep -q amuled ; do sleep 1 ; done
su $USER -c "$WEB --quiet &"
echo "$NAME."
;;
*)
N=/etc/init.d/$NAME
echo "Usage: $N {start|stop|restart|force-reload}" >&2
exit 1
;;
esac
exit 0
Can anyone help me out here?
-
So you compare a script started amuled with a manual started amule. Try to generate a remote.conf using --create-config-from option of amuled before trying with the script.
-
What about the option that aMule can start amuleweb itself? Does it not work on the daemon?
-
I suspect there are different users with different configuration files when starting aMule and when using the init script. Could you please check that?
-
So you compare a script started amuled with a manual started amule. Try to generate a remote.conf using --create-config-from option of amuled before trying with the script.
Wait a minute... What is remote.conf for? I see some differences between the scripts.... Especially the part where amule.conf has a [ExternalConnect] but remote.conf doesn't have that, instead its [EC]..
Well, actually I ended up fixing it by copying amule.conf to remote.conf and changing [ExternalConnect] to [EC] and now all of a sudden the init script is working!
What about the option that aMule can start amuleweb itself? Does it not work on the daemon?
Starting aMule thru the desktop works (it also starts amuled and amuleweb no problem... Just using the daemon is where it doesnt work.
I suspect there are different users with different configuration files when starting aMule and when using the init script. Could you please check that?
I checked that first actually... Only tom (me) currently has an ~/.aMule dir currently. I suspected that maybe root had an amule folder but it doesn't.
Well, I checked amulecmd, amulegui and used the web interface - looks like everything is working okay now. Even though, there was one bit that I thought was a little wierd when i ran the init script - I got this.
tom@ngz:~/.aMule$ sudo /etc/init.d/amule start
Starting amuled: amuled: OnInit - starting timer
Initialising aMuled 2.2.6 using wxGTK2 v2.8.10
Checking if there is an instance already running...
No other instances are running.
ListenSocket: Ok.
amuled: forking to background - see you
amuled.
[b]Enter password for mule connection: [/b]tom@ngz:~/.aMule$
But the remote controls work nonetheless. The log doesnt show any problems either.
2010-01-05 20:10:04: amule.cpp(605): Starting aMuled 2.2.6 using wxGTK2 v2.8.10
2010-01-05 20:10:04: ClientCreditsList.cpp(168): Creditfile loaded, 837 clients are known
2010-01-05 20:10:04: IPFilter.cpp(109): Loading IP-filters 'ipfilter.dat' and 'ipfilter_static.dat'.
2010-01-05 20:10:08: IPFilter.cpp(334): Loaded 269088 IP-ranges from '/home/tom/.aMule/ipfilter.dat'. 0 malformed lines were discarded.
2010-01-05 20:10:08: IPFilter.cpp(334): Loaded 0 IP-ranges from '/home/tom/.aMule/ipfilter_static.dat'. 0 malformed lines were discarded.
2010-01-05 20:10:08: ExternalConn.cpp(159): *** TCP socket (ECServer) listening on 0.0.0.0:4712
2010-01-05 20:10:08: MuleUDPSocket.cpp(81): Created Server UDP-Socket at port 40803
2010-01-05 20:10:08: MuleUDPSocket.cpp(81): Created Client UDP-Socket at port 40802
2010-01-05 20:10:08: ServerList.cpp(84): Loading server.met file: /home/tom/.aMule/server.met
2010-01-05 20:10:08: ServerList.cpp(169): 1 server in server.met found
2010-01-05 20:10:09: DownloadQueue.cpp(171): Found 22 part files
2010-01-05 20:10:09: SharedFileList.cpp(352): Found 20 known shared files
2010-01-05 20:10:09: amule.cpp(803): Connecting
2010-01-05 20:10:09: ServerSocket.cpp(754): Connecting to PeerBooter (88.191.228.66 - 88.191.228.66:7111) using protocol obfuscation.
2010-01-05 20:10:14: RoutingZone.cpp(208): Read 186 Kad contacts
2010-01-05 20:10:15: amule.cpp(846): web server running on pid 5032
2010-01-05 20:10:15: ExternalConn.cpp(217): New external connection accepted
2010-01-05 20:10:15: Connected to Kad (firewalled)
2010-01-05 20:10:15: ThreadScheduler.cpp(308): ThreadScheduler: Completed task 'AICH Syncronizing', 0 tasks remaining.
2010-01-05 20:10:15: ServerConnect.cpp(190): Connected to PeerBooter (88.191.228.66:7111)
2010-01-05 20:10:15: ExternalConn.cpp(251): Connecting client: aMuleweb 2.2.6
2010-01-05 20:10:15: ExternalConn.cpp(306): Access granted.
2010-01-05 20:10:16: ServerConnect.cpp(263): Connection established on: PeerBooter
2010-01-05 20:10:16: Connected to PeerBooter with HighID
2010-01-05 20:10:16: ServerSocket.cpp(417): New clientid is 386940226
2010-01-05 20:10:16: ServerMessage: server version 17.15 (lugdunum)
2010-01-05 20:10:16: ServerMessage: !=>
2010-01-05 20:10:16: ServerMessage: !=> PeerBooter 1.0
2010-01-05 20:10:16: ServerMessage: !=> PEERATES.NET, the eDonkey servers that you can trust.
2010-01-05 20:10:16: ServerMessage: !=>
2010-01-05 20:10:16: ServerMessage: !=> notice that only the free and licit contents are indexed by this server.
2010-01-05 20:10:16: ServerMessage: !=>
2010-01-05 20:10:16: ServerMessage: !=> http://edk.peerates.net
2010-01-05 20:10:16: ServerMessage: !=> contact@peerates.net
2010-01-05 20:10:16: ServerMessage: !=>
2010-01-05 20:10:17: Connected to Kad (ok)
2010-01-05 20:12:59: ExternalConn.cpp(217): New external connection accepted
2010-01-05 20:12:59: ExternalConn.cpp(251): Connecting client: amule-remote 0x0001
2010-01-05 20:12:59: ExternalConn.cpp(306): Access granted.
2010-01-05 20:13:09: ExternalConn.cpp(116): External connection closed.
2010-01-05 20:16:14: ExternalConn.cpp(217): New external connection accepted
2010-01-05 20:16:14: ExternalConn.cpp(251): Connecting client: aMulecmd 2.2.6
2010-01-05 20:16:14: ExternalConn.cpp(306): Access granted.
2010-01-05 20:16:19: ExternalConn.cpp(116): External connection closed.
If its not broke, don't fix it! hehehe... Thaanks all!
-
Wait a minute... What is remote.conf for?
amule and amuled use amule.conf, while the EC clients (amulecmd, amuleweb, amulegui) use remote.conf.
-
Wait a minute... What is remote.conf for?
amule and amuled use amule.conf, while the EC clients (amulecmd, amuleweb, amulegui) use remote.conf.
oic silly me! Never noticed it before....
Although I am still puzzled when the script is started it prompts for a password then promptly exits??
The passwords I set are in the files and both amuleGUI and amuleweb work, just wierd
-
You've set the right working dir in /etc/default/amule?