VPS difficulties
Locked
12
12
 
|
If you mean by removing the '-m32' flag, it didn't work for me. I can't
remember the error messages. -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html |
|
|
In reply to this post by Pharo Smalltalk Users mailing list
Bizarre. I've created a new VirtualBox image of Debian and now this solution
no longer works! I'm still getting the thread priority warning. So this solution appears to be unreliable. <sigh> On Fri, 23 Nov 2018 at 04:02, horrido <horrido.hobbies@> wrote: > 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. > 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 </quote> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html |
|
|
> On 2 Dec 2018, at 18:40, horrido <[hidden email]> wrote: > > Bizarre. I've created a new VirtualBox image of Debian and now this solution > no longer works! I'm still getting the thread priority warning. So this > solution appears to be unreliable. Why use Debian (not that it is bad, it is just a bit more technical) ? I think you would have less problems using Ubuntu (it is just as open, it is what everybody else is using and it is much more user friendly). > <sigh> > > > On Fri, 23 Nov 2018 at 04:02, horrido <horrido.hobbies@> wrote: > >> 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. >> > > 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 > </quote> > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html |
|
|
In reply to this post by horrido
That is strange. Can you post your "/etc/security/limits.d/pharo.conf" file? cheers -ben On Mon, 3 Dec 2018 at 01:42, horrido <[hidden email]> wrote: Bizarre. I've created a new VirtualBox image of Debian and now this solution |
|
|
In reply to this post by Sven Van Caekenberghe-2
I've switched over to Ubuntu Server 18.04 LTS. I've repeated all the steps to
arrive at Pharo installation. I'm still having the same problem: pthread_setschedparam failed. Here's my /etc/security/limits.d/pharo.conf: * hard rtprio 2 * soft rtprio 2 Sven Van Caekenberghe-2 wrote >> On 2 Dec 2018, at 18:40, horrido < > horrido.hobbies@ > > wrote: >> >> Bizarre. I've created a new VirtualBox image of Debian and now this >> solution >> no longer works! I'm still getting the thread priority warning. So this >> solution appears to be unreliable. > > Why use Debian (not that it is bad, it is just a bit more technical) ? > > I think you would have less problems using Ubuntu (it is just as open, it > is what everybody else is using and it is much more user friendly). > >> > <sigh> >> >> >> On Fri, 23 Nov 2018 at 04:02, horrido <horrido.hobbies@> wrote: >> >>> 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. >>> >> >> 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 >> </quote> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html |
|
|
At https://linux.die.net/man/5/limits.conf I read "note that all limit settings are set per login." You haven't mentioned whether you logged out and back in again? cheers -ben On Mon, 3 Dec 2018 at 23:17, horrido <[hidden email]> wrote: I've switched over to Ubuntu Server 18.04 LTS. I've repeated all the steps to |
|
|
Yes, I did. I even rebooted Ubuntu.
Given that this problem occurs for both Debian and Ubuntu, there must be some commonality that hasn't been documented. Ben Coman wrote > At https://linux.die.net/man/5/limits.conf > I read "note that all limit settings are set per login." > You haven't mentioned whether you logged out and back in again? > > cheers -ben > > On Mon, 3 Dec 2018 at 23:17, horrido < > horrido.hobbies@ > > wrote: > >> I've switched over to Ubuntu Server 18.04 LTS. I've repeated all the >> steps >> to >> arrive at Pharo installation. I'm still having the same problem: >> pthread_setschedparam failed. >> >> Here's my /etc/security/limits.d/pharo.conf: >> >> * hard rtprio 2 >> * soft rtprio 2 >> >> >> >> Sven Van Caekenberghe-2 wrote >> >> On 2 Dec 2018, at 18:40, horrido < >> >> > horrido.hobbies@ >> >> > > wrote: >> >> >> >> Bizarre. I've created a new VirtualBox image of Debian and now this >> >> solution >> >> no longer works! I'm still getting the thread priority warning. So >> this >> >> solution appears to be unreliable. >> > >> > Why use Debian (not that it is bad, it is just a bit more technical) ? >> > >> > I think you would have less problems using Ubuntu (it is just as open, >> it >> > is what everybody else is using and it is much more user friendly). >> > >> >> >> > > <sigh> >> >> >> >> >> >> On Fri, 23 Nov 2018 at 04:02, horrido <horrido.hobbies@> wrote: >> >> >> >>> 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. >> >>> >> >> >> >> 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 >> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html |
|
|
In reply to this post by horrido
sven@ubuntu:~/Documents/pharo7$ uname -a
Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux sven@ubuntu:~/Documents/pharo7$ cat /etc/issue Ubuntu 18.04.1 LTS sven@ubuntu:~/Documents/pharo7$ id uid=1000(sven) gid=1000(sven) groups=1000(sven),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),113(lpadmin),128(sambashare) sven@ubuntu:~/Documents/pharo7$ cat /etc/security/limits.d/pharo.conf * hard rtprio 2 * soft rtprio 2 sven@ubuntu:~/Documents/pharo7$ ls -lah /etc/security/limits.d/pharo.conf -rw-r--r-- 1 root root 50 Apr 30 2018 /etc/security/limits.d/pharo.conf sven@ubuntu:~/Documents/pharo7$ pwd /home/sven/Documents/pharo7 sven@ubuntu:~/Documents/pharo7$ curl get.pharo.org/64/70+vm | bash % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 3054 100 3054 0 0 1961 0 0:00:01 0:00:01 --:--:-- 1960 Downloading the latest 70 Image: http://files.pharo.org/get-files/70/pharo64.zip Pharo.image Downloading the latest pharoVM: http://files.pharo.org/get-files/70/pharo64-linux-stable.zip pharo-vm/pharo Creating starter scripts pharo and pharo-ui sven@ubuntu:~/Documents/pharo7$ ./pharo Pharo.image printVersion [version] 'Pharo7.0.0' 'Pharo-7.0.0+rc1.build.1434.sha.ee53b61de346d1dd58999e239e1c3dc5da069b6d (64 Bit)' sven@ubuntu:~/Documents/pharo7$ file pharo-vm/lib/pharo/5.0-201806281256/pharo pharo-vm/lib/pharo/5.0-201806281256/pharo: ELF 64-bit LSB executable, x86-64, version 1 (SYSV), dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.24, BuildID[sha1]=2778173a7eac63dca9a970146659c2de8fef4160, with debug_info, not stripped sven@ubuntu:~/Documents/pharo7$ ldd pharo-vm/lib/pharo/5.0-201806281256/pharo linux-vdso.so.1 (0x00007ffed93c1000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f21defbc000) libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f21dec1e000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f21de9ff000) libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f21de60e000) /lib64/ld-linux-x86-64.so.2 (0x00007f21df1c0000) sven@ubuntu:~/Documents/pharo7$ ./pharo-ui Pharo.image [normal UI] Do you have a normal user account ? Are the permissions on /etc/security/limits.d/pharo.conf root:root ? > On 3 Dec 2018, at 16:16, horrido <[hidden email]> wrote: > > I've switched over to Ubuntu Server 18.04 LTS. I've repeated all the steps to > arrive at Pharo installation. I'm still having the same problem: > pthread_setschedparam failed. > > Here's my /etc/security/limits.d/pharo.conf: > > * hard rtprio 2 > * soft rtprio 2 > > > > Sven Van Caekenberghe-2 wrote >>> On 2 Dec 2018, at 18:40, horrido < > >> horrido.hobbies@ > >> > wrote: >>> >>> Bizarre. I've created a new VirtualBox image of Debian and now this >>> solution >>> no longer works! I'm still getting the thread priority warning. So this >>> solution appears to be unreliable. >> >> Why use Debian (not that it is bad, it is just a bit more technical) ? >> >> I think you would have less problems using Ubuntu (it is just as open, it >> is what everybody else is using and it is much more user friendly). >> >>> >> <sigh> >>> >>> >>> On Fri, 23 Nov 2018 at 04:02, horrido <horrido.hobbies@> wrote: >>> >>>> 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. >>>> >>> >>> 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 >>> </quote> >>> >>> >>> >>> >>> -- >>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > > > > > > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html |
|
|
Yes, I have a normal account. And, yes, the ownership is root:root.
Sven Van Caekenberghe-2 wrote > sven@ubuntu:~/Documents/pharo7$ uname -a > Linux ubuntu 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 > x86_64 x86_64 x86_64 GNU/Linux > > sven@ubuntu:~/Documents/pharo7$ cat /etc/issue > Ubuntu 18.04.1 LTS > > sven@ubuntu:~/Documents/pharo7$ id > uid=1000(sven) gid=1000(sven) > groups=1000(sven),4(adm),24(cdrom),27(sudo),30(dip),46(plugdev),113(lpadmin),128(sambashare) > > sven@ubuntu:~/Documents/pharo7$ cat /etc/security/limits.d/pharo.conf > * hard rtprio 2 > * soft rtprio 2 > > sven@ubuntu:~/Documents/pharo7$ ls -lah /etc/security/limits.d/pharo.conf > -rw-r--r-- 1 root root 50 Apr 30 2018 /etc/security/limits.d/pharo.conf > > sven@ubuntu:~/Documents/pharo7$ pwd > /home/sven/Documents/pharo7 > > sven@ubuntu:~/Documents/pharo7$ curl get.pharo.org/64/70+vm | bash > % Total % Received % Xferd Average Speed Time Time Time > Current > Dload Upload Total Spent Left > Speed > 100 3054 100 3054 0 0 1961 0 0:00:01 0:00:01 --:--:-- > 1960 > Downloading the latest 70 Image: > http://files.pharo.org/get-files/70/pharo64.zip > Pharo.image > Downloading the latest pharoVM: > http://files.pharo.org/get-files/70/pharo64-linux-stable.zip > pharo-vm/pharo > Creating starter scripts pharo and pharo-ui > > sven@ubuntu:~/Documents/pharo7$ ./pharo Pharo.image printVersion > [version] 'Pharo7.0.0' > 'Pharo-7.0.0+rc1.build.1434.sha.ee53b61de346d1dd58999e239e1c3dc5da069b6d > (64 Bit)' > > sven@ubuntu:~/Documents/pharo7$ file > pharo-vm/lib/pharo/5.0-201806281256/pharo > pharo-vm/lib/pharo/5.0-201806281256/pharo: ELF 64-bit LSB executable, > x86-64, version 1 (SYSV), dynamically linked, interpreter > /lib64/ld-linux-x86-64.so.2, for GNU/Linux 2.6.24, > BuildID[sha1]=2778173a7eac63dca9a970146659c2de8fef4160, with debug_info, > not stripped > > sven@ubuntu:~/Documents/pharo7$ ldd > pharo-vm/lib/pharo/5.0-201806281256/pharo > linux-vdso.so.1 (0x00007ffed93c1000) > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f21defbc000) > libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f21dec1e000) > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 > (0x00007f21de9ff000) > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f21de60e000) > /lib64/ld-linux-x86-64.so.2 (0x00007f21df1c0000) > > sven@ubuntu:~/Documents/pharo7$ ./pharo-ui Pharo.image > > [normal UI] > > Do you have a normal user account ? > Are the permissions on /etc/security/limits.d/pharo.conf root:root ? > >> On 3 Dec 2018, at 16:16, horrido < > horrido.hobbies@ > > wrote: >> >> I've switched over to Ubuntu Server 18.04 LTS. I've repeated all the >> steps to >> arrive at Pharo installation. I'm still having the same problem: >> pthread_setschedparam failed. >> >> Here's my /etc/security/limits.d/pharo.conf: >> >> * hard rtprio 2 >> * soft rtprio 2 >> >> >> >> Sven Van Caekenberghe-2 wrote >>>> On 2 Dec 2018, at 18:40, horrido < >> >>> horrido.hobbies@ >> >>> > wrote: >>>> >>>> Bizarre. I've created a new VirtualBox image of Debian and now this >>>> solution >>>> no longer works! I'm still getting the thread priority warning. So this >>>> solution appears to be unreliable. >>> >>> Why use Debian (not that it is bad, it is just a bit more technical) ? >>> >>> I think you would have less problems using Ubuntu (it is just as open, >>> it >>> is what everybody else is using and it is much more user friendly). >>> >>>> >>> > <sigh> >>>> >>>> >>>> On Fri, 23 Nov 2018 at 04:02, horrido <horrido.hobbies@> wrote: >>>> >>>>> 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. >>>>> >>>> >>>> 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 >>>> </quote> >>>> >>>> >>>> >>>> >>>> -- >>>> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html |
|
|
In reply to this post by horrido
I didn’t read much of this thread but the VPS might give a hint. If you are in a virtualized server and you want to modify kernel parameters the underlying host needs to allow that.
Norbert
|
|
|
Yes, I can confirm that it looks like /etc/security/limits.d settings are not honoured inside an LXC/LXD container on Linux. I am not sure that there is a way around this, as it seems that such limits are part of the technology used to implement containers (and hence it might conflict with them by design as you could then step outside your container's limits). Maybe there is a way around this.
Note that the VM keeps on running fine, despite the warning. It feels as if that warning is a bit aggressive and that there should be an option to silence it. > On 3 Dec 2018, at 17:47, Norbert Hartl <[hidden email]> wrote: > > I didn’t read much of this thread but the VPS might give a hint. If you are in a virtualized server and you want to modify kernel parameters the underlying host needs to allow that. > > Norbert > > >> Am 03.12.2018 um 16:55 schrieb horrido <[hidden email]>: >> >> Yes, I did. I even rebooted Ubuntu. >> >> Given that this problem occurs for both Debian and Ubuntu, there must be >> some commonality that hasn't been documented. >> >> >> >> Ben Coman wrote >>> At https://linux.die.net/man/5/limits.conf >>> I read "note that all limit settings are set per login." >>> You haven't mentioned whether you logged out and back in again? >>> >>> cheers -ben >>> >>> On Mon, 3 Dec 2018 at 23:17, horrido < >> >>> horrido.hobbies@ >> >>> > wrote: >>> >>>> I've switched over to Ubuntu Server 18.04 LTS. I've repeated all the >>>> steps >>>> to >>>> arrive at Pharo installation. I'm still having the same problem: >>>> pthread_setschedparam failed. >>>> >>>> Here's my /etc/security/limits.d/pharo.conf: >>>> >>>> * hard rtprio 2 >>>> * soft rtprio 2 >>>> >>>> >>>> >>>> Sven Van Caekenberghe-2 wrote >>>>>> On 2 Dec 2018, at 18:40, horrido < >>>> >>>>> horrido.hobbies@ >>>> >>>>> > wrote: >>>>>> >>>>>> Bizarre. I've created a new VirtualBox image of Debian and now this >>>>>> solution >>>>>> no longer works! I'm still getting the thread priority warning. So >>>> this >>>>>> solution appears to be unreliable. >>>>> >>>>> Why use Debian (not that it is bad, it is just a bit more technical) ? >>>>> >>>>> I think you would have less problems using Ubuntu (it is just as open, >>>> it >>>>> is what everybody else is using and it is much more user friendly). >>>>> >>>>>> >>>>> >>> <sigh> >>>>>> >>>>>> >>>>>> On Fri, 23 Nov 2018 at 04:02, horrido <horrido.hobbies@> wrote: >>>>>> >>>>>>> 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. >>>>>>> >>>>>> >>>>>> 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 >>>> >> >> >> >> >> >> -- >> Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > |
|
|
On Tue, 4 Dec 2018 at 02:07, Sven Van Caekenberghe <[hidden email]> wrote: Yes, I can confirm that it looks like /etc/security/limits.d settings are not honoured inside an LXC/LXD container on Linux. I am not sure that there is a way around this, as it seems that such limits are part of the technology used to implement containers (and hence it might conflict with them by design as you could then step outside your container's limits). Maybe there is a way around this. Perhaps even this warning should be disabled. We've been operating a long time with the threaded-timer as default with no adverse reports. The warning undermines the confidence of new users and gets in the way of their smooth first experience. Regarding any concern about clock jitter, perhaps the place to put this rtprio advice is in the DelayScheduler class comment, which I guess is where anyone having a problem with jitter would go looking. Here is a pertinent thread... cheers -ben > On 3 Dec 2018, at 17:47, Norbert Hartl <[hidden email]> wrote: |
|
|
I agree totally. We shouldn't do anything to scare away people new to Pharo.
It's a hard enough sell as it is. This kind of thing only undermines my advocacy. Ben Coman wrote > On Tue, 4 Dec 2018 at 02:07, Sven Van Caekenberghe < > sven@ > > wrote: > >> Yes, I can confirm that it looks like /etc/security/limits.d settings are >> not honoured inside an LXC/LXD container on Linux. I am not sure that >> there >> is a way around this, as it seems that such limits are part of the >> technology used to implement containers (and hence it might conflict with >> them by design as you could then step outside your container's limits). >> Maybe there is a way around this. >> >> Note that the VM keeps on running fine, despite the warning. It feels as >> if that warning is a bit aggressive and that there should be an option to >> silence it. >> > > Perhaps even this warning should be disabled. We've been operating a long > time with the threaded-timer as default with no adverse reports. > The warning undermines the confidence of new users and gets in the way of > their smooth first experience. > > Regarding any concern about clock jitter, perhaps the place to put this > rtprio advice is in the DelayScheduler class comment, > which I guess is where anyone having a problem with jitter would go > looking. > Here is a pertinent thread... > http://forum.world.st/Unix-heartbeat-thread-vs-itimer-td4928943i20.html > > cheers -ben > > >> On 3 Dec 2018, at 17:47, Norbert Hartl < > norbert@ > > wrote: >> > >> > I didn’t read much of this thread but the VPS might give a hint. If you >> are in a virtualized server and you want to modify kernel parameters the >> underlying host needs to allow that. >> > >> > Norbert >> > >> > >> >> Am 03.12.2018 um 16:55 schrieb horrido < > horrido.hobbies@ > >: >> >> >> >> Yes, I did. I even rebooted Ubuntu. >> >> >> >> Given that this problem occurs for both Debian and Ubuntu, there must >> be >> >> some commonality that hasn't been documented. >> >> >> >> >> >> >> >> Ben Coman wrote >> >>> At https://linux.die.net/man/5/limits.conf >> >>> I read "note that all limit settings are set per login." >> >>> You haven't mentioned whether you logged out and back in again? >> >>> >> >>> cheers -ben >> >>> >> >>> On Mon, 3 Dec 2018 at 23:17, horrido < >> >> >> >>> horrido.hobbies@ >> >> >> >>> > wrote: >> >>> >> >>>> I've switched over to Ubuntu Server 18.04 LTS. I've repeated all the >> >>>> steps >> >>>> to >> >>>> arrive at Pharo installation. I'm still having the same problem: >> >>>> pthread_setschedparam failed. >> >>>> >> >>>> Here's my /etc/security/limits.d/pharo.conf: >> >>>> >> >>>> * hard rtprio 2 >> >>>> * soft rtprio 2 >> >>>> >> >>>> >> >>>> >> >>>> Sven Van Caekenberghe-2 wrote >> >>>>>> On 2 Dec 2018, at 18:40, horrido < >> >>>> >> >>>>> horrido.hobbies@ >> >>>> >> >>>>> > wrote: >> >>>>>> >> >>>>>> Bizarre. I've created a new VirtualBox image of Debian and now >> this >> >>>>>> solution >> >>>>>> no longer works! I'm still getting the thread priority warning. So >> >>>> this >> >>>>>> solution appears to be unreliable. >> >>>>> >> >>>>> Why use Debian (not that it is bad, it is just a bit more >> technical) >> ? >> >>>>> >> >>>>> I think you would have less problems using Ubuntu (it is just as >> open, >> >>>> it >> >>>>> is what everybody else is using and it is much more user friendly). >> >>>>> >> >>>>>> >> >>>>> >> >>> > <sigh> >> >>>>>> >> >>>>>> >> >>>>>> On Fri, 23 Nov 2018 at 04:02, horrido <horrido.hobbies@> >> wrote: >> >>>>>> >> >>>>>>> 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. >> >>>>>>> >> >>>>>> >> >>>>>> 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 >> >> -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html |
«
Return to Pharo Smalltalk Users
|
1 view|%1 views
| Free forum by Nabble | Edit this page |