Just purchased a new server and installed ASL fresh on the box and still the configuration is not reflected in GUI or after asl -c OR asl -s -f.

Can someone in support offer assistance with this as I am paying for 3 ASL licences but cannot actually get anybody to actually assist.

I have raised a new ticket but I have to be honest and say Im a little disappointed with the support offered to be honest

I love the product but what use is it if its not doing the job it was geared up to do ?

Im trying to be as lighthearted as possible but what used to be a smooth experience is full of niggles now and I really am not sure where its all falling down, so excuse what may be perceived as bullishness ;0)

Can you try 3.0.24 for us?

yum --enablerepo=asl-3.0-testing upgrade

Hello Mike,

i cannot ssh into the server after it going onto the ASL kernel as its now outputting :

ssh xxx@xxxxxxxx-x.someone.com
***************************************************************************
NOTICE TO USERS
This computer system is the private property of its owner.
It is for authorized use only. Users (authorized or unauthorized)
have no explicit or implicit expectation of privacy.

Any or all uses of this system and all files on this system may be
intercepted, monitored, recorded, copied, audited, inspected, and
disclosed to your employer, to authorized site, government, and law
enforcement personnel, as well as authorized officials of government
agencies, both domestic and foreign.

By using this system, the user consents to such interception, monitoring,
recording, copying, auditing, inspection, and disclosure at the
discretion of such personnel or officials. Unauthorized or improper use
of this system may result in civil and criminal penalties and
administrative or disciplinary action, as appropriate. By continuing to
use this system you indicate your awareness of and consent to these terms
and conditions of use. LOG OFF IMMEDIATELY if you do not agree to the
conditions stated in this warning.
****************************************************************************

xxx@xxxxxxxx-x.someone.com password:
PTY allocation request failed on channel 0

This post relates to a new server we purchased ( higher spec ) and had a ticket of 15272 raised - this has been deleted or I cannot find it in the support portal after I allowed access to atomicorp, I presume whoever deleted it could to access the server over SSH like myself...

Someone in support worked on the other server and installed the dev build but it did not help matters and the emails are still coming through.

Logging in works fine for me:

$ ssh -l root <YOUR_IP>
***************************************************************************
NOTICE TO USERS
This computer system is the private property of its owner.
It is for authorized use only. Users (authorized or unauthorized)
have no explicit or implicit expectation of privacy.

Any or all uses of this system and all files on this system may be
intercepted, monitored, recorded, copied, audited, inspected, and
disclosed to your employer, to authorized site, government, and law
enforcement personnel, as well as authorized officials of government
agencies, both domestic and foreign.

By using this system, the user consents to such interception, monitoring,
recording, copying, auditing, inspection, and disclosure at the
discretion of such personnel or officials. Unauthorized or improper use
of this system may result in civil and criminal penalties and
administrative or disciplinary action, as appropriate. By continuing to
use this system you indicate your awareness of and consent to these terms
and conditions of use. LOG OFF IMMEDIATELY if you do not agree to the
conditions stated in this warning.
****************************************************************************

Last login: Tue May 22 21:38:56 2012 from NOYB
[root@<REDACTED> ~]#

Are you sure its not your ssh client? A PTY means either the client isnt requesting a tty, or the account isnt setup to generate a shell. ASL doesnt have anything to do with this, have you checked your system logs and the account to see how it may or may not be configured?



Its not deleted, someone set it to not show in the portal, you should see it now.

Hi Mike,

your ticketing system confused me - correct ticket is 15337 and its not the server you accessed as per below

Definitely cannot access via SSH - The ticket explains in detail.

I was able to execute the script to give you access to the system so hopefully that may help matters.

One reason this can happen is that your system is not setup with /etc/fstab to mount the /dev/pts filesystem, or something is wrong with your /dev/pts filesystem. ASL doesnt do this or touch this, so it sounds like something wasnt setup right with the OS itself perhaps that only manifested itself on reboot.

You can get around the pseudo tty with ssh by passing a command, and in the case of a shell tell it to be interactive:

ssh -l root <YOUR IP> bash -i

$ ssh -l root <YOUR IP> bash -i
***************************************************************************
NOTICE TO USERS
This computer system is the private property of its owner.
It is for authorized use only. Users (authorized or unauthorized)
have no explicit or implicit expectation of privacy.

Any or all uses of this system and all files on this system may be
intercepted, monitored, recorded, copied, audited, inspected, and
disclosed to your employer, to authorized site, government, and law
enforcement personnel, as well as authorized officials of government
agencies, both domestic and foreign.

By using this system, the user consents to such interception, monitoring,
recording, copying, auditing, inspection, and disclosure at the
discretion of such personnel or officials. Unauthorized or improper use
of this system may result in civil and criminal penalties and
administrative or disciplinary action, as appropriate. By continuing to
use this system you indicate your awareness of and consent to these terms
and conditions of use. LOG OFF IMMEDIATELY if you do not agree to the
conditions stated in this warning.
****************************************************************************

[root@ds<REDACTED> ~]#

Looking around on your server, it looks like a modified Centos image, and not a valid one. For example:

[root@ds293802-1 boot]# yum update
Bad id for repo: CentOS5 base, byte = 7
Bad id for repo: CentOS5 updates, byte = 7

Thats an ugly error, and definitely not valid for a Centos box.

Do you know if this system is supposed to be a prestine Centos image, or did your provider modify the OS? Because, as I said, this box definitely is not behaving like a valid Centos image and we only support OSes from the vendor. If they monkeyed around with it, thats going to be a problem. Can you confirm if this is supposed to be a prestine Centos image? Because lots of things look broken on this system.

Hi Mike,

I have contacted them and they have said its a pristine Centos image.

Please check tix as I have just sent some info

I would respectfully disagree with them, you may want to ask them whats up with this:

[root@ds<REDACT> ~]# yum update
Bad id for repo: CentOS5 base, byte = 7
Bad id for repo: CentOS5 updates, byte = 7

Hi Mike,

I presume the asl kernel cannot make any problems like that.

Its presumably something from source and I know I have not augmented it.

I am awaiting response from them which may not be till tomorrow, shall we wait for response ?

I'll tell you one thing, I am reading so much and have picked up a fair bit through this all and in that respect I am quite happy that i have had these problems ;0)

I really appreciate you going the mile with this !

It can not, in fact your system wasnt even running the ASL kernel when I posted that. Somethings not right with either the image, or the OS installer or maybe both as thats a broken Centos image for sure. You cant even update the box.



Perhaps, Scott took a look at it an noticed that a lot of non-standard things are in that image, so maybe your provider "tweaks" the Centos images? Its definitely not standard.



My advice would be to install a known pristine Centos image. Something is wrong with the OS itself. Lots of things dont work correctly, and thats with ASL uninstalled. I've never seen so many weird and broken things all in one place. So either the image is broken, someone "tweaked" it, or maybe the installer is munged. I'd install from a clean image. We even make a free tool to do this for you:

https://www.atomicorp.com/downloads.html

Scroll down to AOOI. That will rebuild the machine remotely using a clean Centos image.

https://www.atomicorp.com/installers/aooi

Scott created AOOI may years ago because of a pesky hosting company that shall go nameless that broke their images too. The only solution was to reinstall.

I'll tell you one thing, I am reading so much and have picked up a fair bit through this all and in that respect I am quite happy that i have had these problems ;0)

I really appreciate you going the mile with this !

Hi Mike,

i would be interested in your opinion on this response form the host - In any eventuality I will use the AOOI script to get things moving.

"Having liaised with our engineers I can confirm that the image we use for provisioning Dedicated Servers is completely unmodified. The particular error you have brought to our attention for 'yum update' has been tested and occurred on another DS we have access to, this appears to be an error with the repository the server is attempting to use and not an issue with the server itself. You will still be able to install package from other repositories."

"Of course if there are further errors you system administrators wish to raise I would be more than happy to deal with them. The question raised about the 'purity' of the image is an interesting one but I have been assured that no modifications have been made."

Im curious as to what is going on - is their anything popping out at you thats a sign of it being tweaked / modified ?

Sure, for example your system is running the CentosPlus kernel, which is not part of a standard Centos image. Someone has to add that.

Linux <REDACTED> 2.6.18-308.4.1.el5.centos.plus #1 SMP Tue Apr 17 21:00:16 EDT 2012 x86_64 x86_64 x86_64 GNU/Linux

I can see the elrepo.repo file installed, thats not part of Centos, the systems broken pts filesystem is something I've never seen and I've been using Redhat since way back in the 90s, you've also got the weird errors from yum, etc. Somethings not right with the image thats for sure, and its not a pristine Centos image I can tell you that.

Just to update on this - I cancelled the server with them due to it not being a standard affair and opted for the VPS product which is more robust.. I have updated the thread started when I was having problems.