Page 7 of 32

Re: New shell server transition

Posted: Fri Mar 02, 2018 4:12 pm
by Guest
All of this is such a big PITA. Can I just stay on the "old" shell server?

Re: New shell server transition

Posted: Fri Mar 02, 2018 5:16 pm
by scott
Guest wrote:
All of this is such a big PITA. Can I just stay on the "old" shell server?


Trying hard not to be cynical why an anonymous poster wants a 12-year old system to stay running... ;)

Seriously though, Bolt is too old, it should have been replaced long ago. And, because of the unique nature of our network, we have to replace the shell server before we can replace the shared hosting servers...

Re: New shell server transition

Posted: Fri Mar 02, 2018 6:14 pm
by patty1
Hey, Scott, some of us are just grateful that Sonic even still offers a shell machine!! :lol: (I couldn't find an applause emoticon...)

Re: New shell server transition

Posted: Sat Mar 03, 2018 9:31 am
by patty1
Ohhhh Scoooooott... Hallooooo.......

/bin/sh: /home/p/patty1/bin/calendar: No such file or directory


Was it a temporary glitch overnight? Unlike the other night, this time all of my files are appearing now. Maybe they just disappeared briefly during the time that cron was trying to find them? Do you know why this is happening?

Re: New shell server transition

Posted: Sat Mar 03, 2018 5:43 pm
by Guest
scott wrote:
Bolt is too old, it should have been replaced long ago. And, because of the unique nature of our network, we have to replace the shell server before we can replace the shared hosting servers...

Fair enough. My sincere apologies for the stupid question.

Re: New shell server transition

Posted: Sun Mar 04, 2018 4:24 pm
by scott
patty1 wrote:
Ohhhh Scoooooott... Hallooooo.......

/bin/sh: /home/p/patty1/bin/calendar: No such file or directory


Was it a temporary glitch overnight? Unlike the other night, this time all of my files are appearing now. Maybe they just disappeared briefly during the time that cron was trying to find them? Do you know why this is happening?


The problem cropped up again, but I caught it and restarted the system.

I haven't figured out the exact problem yet, but I have made some changes to the system that should make it more robust. Again, sorry about the trouble.

-Scott

Re: New shell server transition

Posted: Mon Mar 05, 2018 12:03 pm
by gie
gie wrote:
I'll continue this tomorrow when I can get aid, but although this does allow me to configure a MYINBOX folder and see mail delivered, the next message that arrives flashes an "Unexpected change to folder..." message that goes away before I can read it and the new message is not delivered.

Alpine was compiled without debug?


I switched to trying yet again to get the password file to store.

It would be super helpful if alpine were compiled with debug please.

Then I could possibly figure out more about why it won't encrypt and store with the various ways I've tried to generate and store SSL certificate,

Right now when I try to start with debug I get "Argument Error: unknown flag "d", debugging not compiled in"

Thanks!

Re: New shell server transition

Posted: Mon Mar 05, 2018 1:11 pm
by scott
gie wrote:
gie wrote:
I'll continue this tomorrow when I can get aid, but although this does allow me to configure a MYINBOX folder and see mail delivered, the next message that arrives flashes an "Unexpected change to folder..." message that goes away before I can read it and the new message is not delivered.

Alpine was compiled without debug?


I switched to trying yet again to get the password file to store.

It would be super helpful if alpine were compiled with debug please.

Then I could possibly figure out more about why it won't encrypt and store with the various ways I've tried to generate and store SSL certificate,

Right now when I try to start with debug I get "Argument Error: unknown flag "d", debugging not compiled in"

Thanks!


I'll get it recompiled. Currently we're using the package that came with CentOS 7, not sure why the package maintainer turned off debug in the compilation.

-Scott

Re: New shell server transition

Posted: Mon Mar 05, 2018 6:36 pm
by Guest
Since my Telnet program will not connect to the new shell, I tried connecting to the new shell while logged into the old shell, but that doesn't work either. It just hangs. Are we not allowed to telnet into the new shell from the old shell?

Re: New shell server transition

Posted: Tue Mar 06, 2018 1:53 pm
by gie
Guest wrote:
Since my Telnet program will not connect to the new shell, I tried connecting to the new shell while logged into the old shell, but that doesn't work either. It just hangs. Are we not allowed to telnet into the new shell from the old shell?


I see on https://wiki.sonic.net/wiki/Shell_Acces ... Transition that telnet is no longer allowed:

Shell logins are handled using only ssh -- no more telnet