Freenet daemon not working

[Pajarico]

I have configure and updated it, but when i try to run the daemon:

Code: Select all

bash-2.05b# /etc/init.d/freenet start
 * Starting Freenet now...
grep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
nice: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
sleep: error while loading shared libraries: libm.so.6: cannot open shared object file: No such file or directory
ps: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
cat: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
grep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory                                                  [ !! ]

rm: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory

That is with export LD_ASSUME_KERNEL=2.4.1 uncommented in /etc/init.d/freenet; if i comment it :

Code: Select all

bash-2.05b# /etc/init.d/freenet start
 * Starting Freenet now...                                              [ !! ]

This on amd 64 with glib compiled with nptl and multilib flags.

[Papaver]

I'm having problems with freenet that started as you described. I haven't fixed it, but have made some sort of process. I hope what I've done so far helps you.

You're using NPTL, so that LD_ASSUME_KERNEL=2.4.1 should indeed be commented out.

One problem is with this line in /etc/init.d/freenet:

Code: Select all

nice -n ${FREENET_NICENESS} sudo -u freenet /usr/bin/start-freenet.sh \
                > /var/freenet/freenet.pid

Be default sudo will not pass environment variables on, so you need to edit /etc/sudoers (via the visudo command). In your /etc/sudoers you should see something like this:

Code: Select all

# Reset environment by default
Defaults        env_reset
# Uncomment to allow people in group wheel to export variables
# %Defaults:%wheel !env_reset

Uncomment that last line, so now you have:

Code: Select all

Defaults:%wheel !env_reset

Now it appears to work:

Code: Select all

# /etc/init.d/freenet start
 * Starting Freenet now...                                         [ ok ]
# 

BUT...

Code: Select all

# cat /var/freenet/freenet.log 
Dec 29, 2004 11:13:31 PM (freenet.node.Main, main, NORMAL): Starting Freenet (Fred) 0.6 node, build #60260 on JVM Sun Microsystems Inc.:Java HotSpot(TM) Server VM:1.4.2-gentoo-1104355787
Dec 29, 2004 11:13:32 PM (freenet.node.Node, main, ERROR): Encountered an unexpected error when locking the lockfile '/var/freenet/lock.lck'. Shutting down.
java.io.IOException: Invalid argument
        at sun.nio.ch.FileChannelImpl.lock0(Native Method)
        at sun.nio.ch.FileChannelImpl.tryLock(FileChannelImpl.java:788)
        at java.nio.channels.FileChannel.tryLock(FileChannel.java:967)
        at freenet.node.Node.init(Node.java:3583)
        at freenet.node.Main.main(Main.java:476)
# 

And this is as far as I've made it with this problem tonight. Any further insight on this would be greatly appreciated.

[Pajarico]

Ok, now my looks like this:

Code: Select all

# Reset environment by default
# Defaults      env_reset
# Uncomment to allow people in group wheel to export variables
 Defaults:%wheel        !env_reset

But now sudo complains about something different:

Code: Select all

bash-2.05b# /etc/init.d/freenet start
 * Starting Freenet now...
>>> sudoers file: syntax error, line 18 <<<
sudo: parse error in /etc/sudoers near line 18
sendmail: Cannot open mail:25                                             [ ok ]
bash-2.05b# 

Although '[ok]' is printed it doesn't connect to http://127.0.0.1:8888/

[Pajarico]

Commented again:

Code: Select all

# Defaults:%wheel       !env_reset

Now it works, but is extremely slow, it is normal?

[Papaver]

Is it freenet itself that is extremely slow? That's normal, especially for the first few days you're running it.

[Arker]

Did you ever figure out the problem with that Java IOException regarding the lockfile? I'm having the same issue.

Cheers,
~djc

[Pajarico]

Is it freenet itself that is extremely slow? That's normal, especially for the first few days you're running it.

I've used freenet a pair of times, and io starting to think that it is not only slow but extremely unstable or buggy. It just sits there, can't connect with anything and totally kills my connection, even when there is no network traffic at all.

[Ribs]

I have configure and updated it, but when i try to run the daemon:

Code: Select all

bash-2.05b# /etc/init.d/freenet start
 * Starting Freenet now...
grep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
nice: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
sleep: error while loading shared libraries: libm.so.6: cannot open shared object file: No such file or directory
ps: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
cat: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory
grep: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory                                                  [ !! ]

rm: error while loading shared libraries: libc.so.6: cannot open shared object file: No such file or directory

Hi, I stumbled accross this thread the other day. I was having the same problem with Freenet. The above problem is caused by glibc.

The current stable version of glibc in Gentoo is either compiled with, or without nptl. Now, if you use a nptl system (which is a good thing(tm)) and the current stable version of glibc (2.3.4.20040808-r1, at time of writing), then you will have a system which does not run well with programs that don't like nptl.

Gentoo recently changed the policy towards glibc. It now compiles it twice, once with, and once without nptl. So you can use the non-nptl version when required, as it is in this case. So the soultion is to use a ~x86 version of glibc for the time being, so you get a glibc which is more compatible. That should kill your shared libraries errors.

This thread is so old I guess everyone already has the soultion, but I thought it worth posting anyway, just in case someone has the same problem.

After fixing glibc, I got the Freenet not working with the following in /var/freenet/freenet.stderr.log:

Code: Select all

Exception in thread "main" java.lang.NoClassDefFoundError: freenet/node/Main

Use the sudoers trick discuessed above to fix this.

-Ribs.

[Pajarico]

Thanks for the tip. I updated glibc and it compiled both version (nptl and nptl-less). Now freenet starts and stops without dumping errors.