VPS difficulties

Using zeroconf, I installed 32-bit Pharo under 64-bit Debian. Pharo refused
to run – it threw up a bunch of errors.



Mariano Martinez Peck wrote
> Run Pharo 32 bits and install 32 bit libs...
>
> On Wed, Nov 21, 2018, 21:07 Richard Kenneth Eng <

> horrido.hobbies@





--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

horrido wrote
> it threw up a bunch of errors.

Can you be more specific and did you try Mariano's suggestion about 32-bit
libs?



-----
Cheers,
Sean
--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Just use 64 bit Pharo 7 on a 64 bit Linux and be done with all this mess.

I think Sven is probably right - but my notes show a DO installation from 5 months ago with:

He's got a 32 bit library that he wants to use, that won't work with a 64
bit VM.
Of course, recompiling the library for 64 bit is an option, too, but
probably more complicated.

Cheers,
Hans-Martin

Am 22. November 2018 9:21:47 vorm. schrieb Sven Van Caekenberghe
<[hidden email]>:

I tried recompiling the SHA256 library without the '-m32' flag and 64-bit
Pharo seg faulted:

pthread_setschedparam failed: Operation not permitted
This VM uses a separate heartbeat thread to update its internal clock
and handle events.  For best operation, this thread should run at a
higher priority, however the VM was unable to change the priority.  The
effect is that heavily loaded systems may experience some latency
issues.  If this occurs, please create the appropriate configuration
file in /etc/security/limits.d/ as shown below:

cat <<END | sudo tee /etc/security/limits.d/pharo.conf
*      hard    rtprio  2
*      soft    rtprio  2
END

and report to the pharo mailing list whether this improves behaviour.

You will need to log out and log back in for the limits to take effect.
For more information please see
https://github.com/OpenSmalltalk/opensmalltalk-vm/releases/tag/r3732#linux

Segmentation fault Wed Nov 21 22:10:27 2018


/home/richard/pharo/pharo-vm/lib/pharo/5.0-201806281256/pharo
Pharo VM version: 5.0-201806281256  Thu Jun 28 13:04:44 UTC 2018 gcc 4.8
[Production Spur 64-bit VM]
Built from: CoInterpreter VMMaker.oscog-eem.2401 uuid:
29232e0e-c9e3-41d8-ae75-519db862e02c Jun 28 2018
With: StackToRegisterMappingCogit VMMaker.oscog-eem.2401 uuid:
29232e0e-c9e3-41d8-ae75-519db862e02c Jun 28 2018
Revision: VM: 201806281256
https://github.com/OpenSmalltalk/opensmalltalk-vm.git Date: Thu Jun 28
14:56:30 2018 CommitHash: a8a1dc1 Plugins: 201806281256
https://github.com/OpenSmalltalk/opensmalltalk-vm.git
Build host: Linux travis-job-46342785-b1c1-4811-8c3c-9b2a88ae7ecc
4.4.0-101-generic #124~14.04.1-Ubuntu SMP Fri Nov 10 19:05:36 UTC 2017
x86_64 x86_64 x86_64 GNU/Linux
plugin path: /home/richard/pharo/pharo-vm/lib/pharo/5.0-201806281256
[default: /home/richard/pharo/pharo-vm/lib/pharo/5.0-201806281256/]


C stack backtrace &amp; registers:
rax 0x17be8f40 rbx 0x17be8dd0 rcx 0x17be8ff8 rdx 0x17be8e88
rdi 0x17be8ba8 rsi 0x17be8ba8 rbp 0x17be8d18 rsp 0x17be90b0
r8  0x17be85e8 r9  0x17be86a0 r10 0x17be8758 r11 0x17be8810
r12 0x17be88c8 r13 0x17be8980 r14 0x17be8a38 r15 0x17be8af0
rip 0x17be9168
*[0x7ffc17be9168]

blah, blah, blah

----------

The &quot;pthread_setschedparam failed&quot; error is concerning, too.



&lt;quote author=&quot;Hans-Martin&quot;>
He's got a 32 bit library that he wants to use, that won't work with a 64
bit VM.
Of course, recompiling the library for 64 bit is an option, too, but
probably more complicated.

Cheers,
Hans-Martin

Am 22. November 2018 9:21:47 vorm. schrieb Sven Van Caekenberghe
&lt;sven@&gt;:





--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

I ran 32-bit Pharo under 64-bit Debian and got this error:

[1] 8127
richard@debian:~/pharo32$ could not find display driver vm-display-X11;
either:
  - check that
/home/richard/pharo32/pharo-vm/lib/pharo/5.0-201806281256//vm-display-X11.so
exists, or
  - use the '-plugins <path>' option to tell me where it is, or
  - remove DISPLAY from your environment.
./pharo-ui: line 11:  8131 Aborted                 "$DIR"/"pharo-vm/pharo"
"$@"

----------

I thought you could always run 32-bit software in a 64-bit OS, but I guess
I'm wrong.



Sean P. DeNigris wrote




--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Those errors are not related to a 32 or 64 bits problem. The issue looks
like you've launched pharo-ui which looks for a physical screen that
isn't there. Are you trying to run pharo-ui in a debian VPS ?

You should run 'pharo' and 'pharo-ui', something like this:

$ pharo myApplication.image

Search on google for 'pharo headless', you should find plenty of example.

HTH,

Fred

On 22/11/2018 13:31, horrido wrote:

I'm running 64-bit Debian in a VirtualBox image on my Mac.

When I install 64-bit Pharo, it works fine. When I install 32-bit Pharo, I
get the error message below. What's the difference??? Why can one find the
display driver and the other can't? This makes no sense.

Earlier, people have been telling me to use './pharo-ui Pharo.image &'. Is
this no longer kosher? What am I doing wrong?



Fred Kaiser Borg wrote




--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

Using Linux requires certain skills/knowledge, this has nothing to do with Pharo or Smalltalk.

To run 32-bit binaries on a 64-bit system you need 32-bit libraries.

This might help (although maybe it is not totally up to date for Pharo 7)

https://github.com/svenvc/pharo-server-tools/blob/master/ubuntu-32bit-support-on-64bit.sh

You can check the dependencies of binaries and dynamic libraries with ldd. They have to be resolved correctly.

$ uname -a
Linux sigfox-1 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18 18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

$ file bin/pharo-vm/pharo
bin/pharo-vm/pharo: ELF 32-bit LSB executable, Intel 80386, version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.2, for GNU/Linux 2.6.24, BuildID[sha1]=dcf3b690e793d6960e1dbccd36bd0b3938019471, not stripped

$ ldd bin/pharo-vm/pharo
        linux-gate.so.1 =>  (0xf7730000)
        libm.so.6 => /lib/i386-linux-gnu/libm.so.6 (0xf76d2000)
        libdl.so.2 => /lib/i386-linux-gnu/libdl.so.2 (0xf76cd000)
        libpthread.so.0 => /lib/i386-linux-gnu/libpthread.so.0 (0xf76b0000)
        libc.so.6 => /lib/i386-linux-gnu/libc.so.6 (0xf74fa000)
        /lib/ld-linux.so.2 (0x565fe000)

pharo and pharo-ui are just scripts

I would also strongly recommend not using native (FFI) libraries (at first).

You must also understand the difference between a UI based and headless system.

Okay, I've resolved everything. First, the reason why I'm getting the
'pthread_setschedparam failed' error when I run Pharo under Debian is
because it must be run as 'root'! Don't ask me why, but that's the reason
why Pharo can't set thread priorities. (This wasn't an issue under Ubuntu
Server – go figure.)

Second, I am now using Pharo's own SHA256 class. It's probably not as secure
(because it doesn't use a salt value) and not as quick to execute (not being
C code), but for my purpose, it doesn't really matter.

So I can use DigitalOcean or OVH to run my web server in a VPS.



--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

It can't find the display drivers since the appropriate 32 bit libraries
are missing. Use the 'ldd' command on the VM binary and on the shared
libraries in its directory to find out which ones you're missing.

Cheers,
Hans-Martin

Am 22. November 2018 4:22:19 nachm. schrieb horrido
<[hidden email]>:

By the way, after looking at password hashing algorithms and what the experts
say about them, I've decided to implement an interface to the Argon2 library
(see https://password-hashing.net/argon2-specs.pdf for a whitepaper). The
algorithm is designed to be far more resistant against cracking than md5 or
sha-based algorithms and even bcrypt.

The interface is designed to be very easy to use. In the simplest case
(without tuning the algorithm's parameters) password hashing is performed
like this:
    hashedPassword := Argon2 new randomizeSalt: 16; hashPassword:
newPassword.
verifying that a user has given the correct password:
    ok := Argon2 new verifyPassword: enteredPassword hash: hashedPassword.

Find the code at https://github.com/hamamo/pharo-argon2. Currently it only
has library names for 32-bit and 64-bit Linux - if someone adds MacOSX and
Windows support I would merge that.
Sorry I don't yet know how to use Metacello or other mechanisms to load it
into an image with a few lines of code.

Cheers,
Hans-Martin



--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

This works! Everything is copacetic.



On Fri, 23 Nov 2018 at 04:02, horrido &lt;horrido.hobbies@&gt; wrote:

Good to hear.  But you shouldn't need to run Pharo as root,
just be root to create this config file....
cat <<END | sudo tee /etc/security/limits.d/pharo.conf
*      hard    rtprio  2
*      soft    rtprio  2
END

cheers -ben
&lt;/quote>




--
Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

On Wed, Nov 21, 2018 at 07:06:08PM -0500, Richard Kenneth Eng wrote:
> I'm creating the competition website using Pharo and Teapot. For
> encryption, I'm using Pierce Ng's PasswordCrypt, which requires a 32-bit C
> library. This means I must run 32-bit Pharo.

PasswordCrypt can be built as a 64-bit library.

(Was away on vacation. Just saw this.)

Pierce