Hey guys, im trying to setup OSBOT on a Raspberry pi. I cannot get it to work with mirror mode, i'm getting the error "Could not load stream library".

Investigating the logs i discovered that osbot created two files on /tmp/*.so

root@debian:/# file /tmp/*.so
/tmp/rqww8634908137993072872.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=5bcea5142a8fc64f2aa426afbe191b3f5f2887cf, stripped
/tmp/wqq4820335396777126421.so:  ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=4dbf0e9e11e80b7cd37b84d9246f735e47a2d0ba, stripped

By using linux command 'strings' i was able to discover what "/tmp/rqww8634908137993072872.so" was:

"strings /tmp/rqww8634908137993072872.so" showed that this file contained a string "Unable to get pid of LinuxThreads manager thread" then i found the corresponding .so file in my AARM64 JDK:

root@debian:~/Downloads/jdk1.8.0_361$ grep -al -- "Unable to get pid of Linux" ./jre/lib/aarch64/*.so 
./jre/lib/aarch64/libattach.so

I think that its possible to just copy paste this file into the /tmp/ dir and it will do the trick, cp ./jre/lib/aarch64/libattach.so /tmp/rqww8634908137993072872.so

But i was not able to do the same for wqq4820335396777126421.so. I cant find any corresponding binary in my AARM64 JDK and i cant find any strings of this binary in the internet as well. It is possible for you devs provide this .so compiled as AARM64, (or release the source code :P)?

Also, another question: What are the advantages of mirror? It decreases the chances of you getting banned?

• Mirror client version: OSBot 2.6.61
• Console output / terminal output:

  • [INFO][01/21 12:42:28 PM]: Loaded 1 RS accounts!
    [INFO][01/21 12:42:28 PM]: Welcome to OSBot 2.6.61!
    [INFO][01/21 12:42:49 PM]: Updated injection hooks for client revision : 210!
    [DEBUG][Bot #1][01/21 12:42:49 PM]: Initializing mirror client bot...
    [INFO][01/21 12:42:51 PM]: Started bot #1
    [ERROR][Bot #1][01/21 12:42:51 PM]: nattachfail
    java.lang.RuntimeException: s3
    	at client.sYAf.cckd(Unknown Source)
    	at client.ob.thvv(Unknown Source)
    	at client.emu.Av.run(Unknown Source)
    Caused by: java.lang.UnsatisfiedLinkError: /tmp/rqww8634908137993072872.so: /tmp/rqww8634908137993072872.so: cannot open shared object file: No such file or directory (Possible cause: can't load AMD 64-bit .so on a AARCH64-bit platform)
    	at java.lang.ClassLoader$NativeLibrary.load(Native Method)
    	at java.lang.ClassLoader.loadLibrary0(ClassLoader.java:1937)
    	at java.lang.ClassLoader.loadLibrary(ClassLoader.java:1820)
    	at java.lang.Runtime.load0(Runtime.java:782)
    	at java.lang.Runtime.load(Runtime.java:770)
    	... 3 more
    [ERROR][Bot #1][01/21 12:42:52 PM]: legacyload
    java.lang.ClassNotFoundException: com.sun.tools.attach.spi.AttachProvider
    	at java.lang.ClassLoader.findClass(ClassLoader.java:523)
    	at org.osbot.k.findClass(ev:87)
    	at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
    	at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
    	at java.lang.Class.forName0(Native Method)
    	at java.lang.Class.forName(Class.java:264)
    	at client.KtVM.<clinit>(Unknown Source)
    	at client.sYAf.sxxu(Unknown Source)
    	at client.sYAf.to(Unknown Source)
    	at client.nat.stream.Stream.cckd(Unknown Source)
    	at client.ob.thvv(Unknown Source)
    	at client.emu.Av.run(Unknown Source)
    [ERROR][Bot #1][01/21 12:42:53 PM]: Could not load stream library
    java.lang.RuntimeException: Could not load stream library
    	at client.nat.stream.Stream.cckd(Unknown Source)
    	at client.ob.thvv(Unknown Source)
    	at client.emu.Av.run(Unknown Source)
    Caused by: java.lang.RuntimeException: s2
    	... 3 more

     

• Crash report if a crash occurred: N/A
• Script that you ran: N/A
• Hooks that failed: N/A
• JVM/Browser bit version (AARM64😞

  • root@debian:/# java -version
    java version "1.8.0_361"
    Java(TM) SE Runtime Environment (build 1.8.0_361-b09)
    Java HotSpot(TM) 64-Bit Server VM (build 25.361-b09, mixed mode)

     

got same problem here. 

 

First of all, mirror probably wont run great on a RPi since it is resource intensive. For any linux distributions that will want to run mirror there is a workaround that you need to apply since the suntools.awt in most linux java distributions wont work with mirror.