Threaded Mode | Linear Mode

simoncn · 11-03-2013, 13:23

@Rairwave:

Please can you try the following commands and post the output:

/var/packages/JavaManager/target/Java/jre/bin/java -version

ldd /var/packages/JavaManager/target/Java/jre/bin/java

objdump -p /var/packages/JavaManager/target/Java/jre/bin/java

Many thanks!

Simon

Rairwave · 11-03-2013, 15:55

(11-03-2013 13:23)simoncn Wrote: @Rairwave:

Please can you try the following commands and post the output:

/var/packages/JavaManager/target/Java/jre/bin/java -version

ldd /var/packages/JavaManager/target/Java/jre/bin/java

objdump -p /var/packages/JavaManager/target/Java/jre/bin/java

Many thanks!

Simon

BusyBox v1.16.1 (2013-03-01 01:11:16 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

XXXXXX> /var/packages/JavaManager/target/Java/jre/bin/java -version
java version "1.6.0_43"
Java™ SE Runtime Environment (build 1.6.0_43-b01)
Java HotSpot™ Server VM (build 20.14-b01, mixed mode)
XXXXXX> ldd /var/packages/JavaManager/target/Java/jre/bin/java
-ash: ldd: not found
XXXXXX> objdump -p /var/packages/JavaManager/target/Java/jre/bin/java
-ash: objdump: not found
XXXXXX> whoami
root
XXXXXX>

simoncn · 11-03-2013, 17:03

(11-03-2013 15:55)Rairwave Wrote: BusyBox v1.16.1 (2013-03-01 01:11:16 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

XXXXXX> /var/packages/JavaManager/target/Java/jre/bin/java -version
java version "1.6.0_43"
Java™ SE Runtime Environment (build 1.6.0_43-b01)
Java HotSpot™ Server VM (build 20.14-b01, mixed mode)
XXXXXX> ldd /var/packages/JavaManager/target/Java/jre/bin/java
-ash: ldd: not found
XXXXXX> objdump -p /var/packages/JavaManager/target/Java/jre/bin/java
-ash: objdump: not found
XXXXXX> whoami
root
XXXXXX>

Thanks very much! Even though the last two commands weren't found (which surprises me), the output from the first command provides useful information.

This appears to be a regular desktop Oracle x86 JRE, not the embedded JRE that is recommended for MinimServer. The symptoms suggest that the regular desktop JRE isn't fully compatible with the glibc version in the DSM firmware.

However, I've just looked at the desktop JRE and I can't spot an obvious incompatibility. Without access to an x86 Synology NAS, I don't think I can make much more progress with diagnosing the casue of the problem.

Rairwave · 11-03-2013, 21:55

(11-03-2013 17:03)simoncn Wrote: This appears to be a regular desktop Oracle x86 JRE, not the embedded JRE that is recommended for MinimServer. The symptoms suggest that the regular desktop JRE isn't fully compatible with the glibc version in the DSM firmware.

However, I've just looked at the desktop JRE and I can't spot an obvious incompatibility. Without access to an x86 Synology NAS, I don't think I can make much more progress with diagnosing the casue of the problem.

@simoncn, please have a look at the following output. To be clear I removed the java se jre and the Synology java manager. Afterwards I installed the java embedded by patters Synology package. And rebooted the NAS and restarted MinimServer twice to be sure.

BusyBox v1.16.1 (2013-03-01 01:11:16 CST) built-in shell (ash)
Enter 'help' for a list of built-in commands.

XXXXXX> ps -w | grep minim
9528 minimser 2616 S tail -n 1 -f /volume1/@tmp/minimstdinpipe
9529 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9532 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9533 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9534 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9535 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9536 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9537 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9538 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9539 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9542 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9545 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9547 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9551 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9552 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9560 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9561 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9562 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9563 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9564 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9565 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9566 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9567 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9568 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9569 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9570 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9571 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9572 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
9573 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
11079 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
11080 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
11081 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
11082 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
11085 minimser 386m S /volume1/@appstore/java6/jre/bin/java -jar /volume1/@appstore/MinimServer/lib/minimserver.jar --nohup
11476 root 2548 S grep minim
XXXXXX> /volume1/@appstore/java6/jre/bin/java -version
java version "1.6.0_38"
Java SE Embedded Runtime Environment (build 1.6.0_38-b05, headless)
Java HotSpot™ Embedded Client VM (build 20.13-b02, mixed mode)
XXXXXX>

Is it a bad thing to have so many java processes? MinimServer is running fine, not a problem to me. Just curious :-)

simoncn · 11-03-2013, 23:56

(11-03-2013 21:55)Rairwave Wrote: @simoncn, please have a look at the following output. To be clear I removed the java se jre and the Synology java manager. Afterwards I installed the java embedded by patters Synology package. And rebooted the NAS and restarted MinimServer twice to be sure.

........

Is it a bad thing to have so many java processes? MinimServer is running fine, not a problem to me. Just curious :-)

Thanks very much for trying this. From this evidence, it seems clear that the level of Linux in the Synology x86 models (glibc 2.3.6) is so old that it doesn't support pthreads.

In the last few weeks, I've investigated reports by two different users, both on Synology x86, of an intermittent problem with tracks failing to start playing. I'm beginning to suspect that this large number of java processes and the lack of pthreads support might be related to these problems. Have you seen anything like this on your NAS?

simoncn · (This post was last modified: 18-03-2013 14:30 by simoncn.)

A new version of the Synology installation package is now available. This should report the status correctly. Please download the new version from this link and let us know whether it fixes the status reporting problem in the package center when using Java Manager. The 'ps -w' output will still show multiple java processes, and there's no way to prevent this.