Setarch command and segmentation error...

[philz]

anyone know how to get the setarch command onto a VPS? as it seems my VPS was upgraded kernal wise and now one of the apps (probably the most important one that we use constantly) dosent work. After nearly 3 days of research it seems i need to be able to run this command as the only workaround besides changeing kernals:

setarch i686 -X ./server_linux -PID=tsserver2.pid

and this is the only option i have as i have no idea how to change kernals and sounds way to dangerous to me (if i even can since this is a VPS after all!).

The issue has to deal with some special modification to the red-hat kernals, as the generic ones have no issue at all and same with other flavors! As whatever they did causes segmentation faults and not just with teamspeak, seems like other apps have the issue...

Any adivice would definetly eb welcomend!!

Thanks in advance,
Philz

[Andre]

For the teamspeak server try to use:

$ setarch i386 -X ./teamspeak2-server_startscript start

Most likely the segmentation faults are related to the noexec bit in the kernel being enabled on the node in question. We can turn this off, however this would require a reboot of the node so we'd have to schedule this. If this is important to you then please open a support ticket with a reference to this thread, then we will take care of this as soon as possible.

On a sidenote: on a VPS it is indeed not possible for you to change anything about the kernel as the kernel is being used by all VPS's on the node.

[philz]

Hmm... seems like it dosent flat out like the setarch command. As here is a console cap:

**@** [~/tss2_rc2]# ./teamspeak2-server_startscript start
starting the teamspeak2 server
./teamspeak2-server_startscript: line 29: setarch: command not found
**@** [~/tss2_rc2]# ./teamspeak2-server_startscript start
starting the teamspeak2 server
./teamspeak2-server_startscript: line 29: $: command not found
**@** [~/tss2_rc2]# uname -m
i686

That was when i used the setarch command in the script (had to change a couple thigns as it isnt the same...) but I also tried i686 as that is what uname gave me (but most not work right as arent xeons i386 *confused*)

But if i do it to the startscript:

**@** [/home/inblog/tss2_rc2]# setarch i386 -X ./teamspeak2-server_startscript start
bash: setarch: command not found
**@** [/home/inblog/tss2_rc2]# setarch i686 -X ./teamspeak2-server_startscript start
bash: setarch: command not found

that is when i do it the other way with just the script set for the setarch (acording to teamspeaks forums you can do it either way as i have done both too...)

But if i am doing everything wright and there is no other way i guess i'll go ahead and make the support ticket, but i would rather avoid haveing to be an inconvince to my whole node. On a side note, just want to check, did the kernal change over the weekend with all those issues? As it worked fine till after the final fdisk and/or you put the old drive back in...?

Thanks in advance,
Philz

[philz]

Just as an update to anyone else that is curious, seems to me that the setarch command is fruitless on a VPS (after the techs set the command up on my VPS, as everyone on the Teamspeak forums figured it is pre-installed with the kernal update, so another reason why i think virtuozzo gimps it...). Maybe due to some security issue or something with virtuozzo. As it just dosent seem to work, or seems like it does but to no avail (even no error message or script message in some cases).

-Philz

[Andre]

Just to update this thread: we've made some changes on this node and this issue should now be solved.

[philz]

I has been! I can run everything prefectly fine again, no problems.

DEHE, simply the best host you can ever have, and so understanding to!

Now back to working on my companys site instead of trying to get teamspeak back up :lol:

[imported_sole]

Just to update this thread: we've made some changes on this node and this issue should now be solved.

At last someone in the same boat as me where the setarch function does not work with Virtuzzo.
Sorry to say im not hosted with you guys but I am desperate to find a solution for the same problem with teamspeak.
Could you tell me what the changes were you made to the node to fix this so I can relay them to my hosts, although they have said they will look into upgrading the kernel on the whole node I don't want that to be just because of little old me!!

Thanks in advance for your time and answsers.

Sole

[Andre]

Hi Sole,

If they are running Virtuozzo and are running the latest 2.6 kernel, they have to disable the noexec bit in the kernel and then reboot the node.

I've let Rus know how to do that.

[imported_sole]

Hi Sole,

If they are running Virtuozzo and are running the latest 2.6 kernel, they have to disable the noexec bit in the kernel and then reboot the node.

I've let Rus know how to do that.

yes is Virtuozzo and a 2.6 kernel, Rus!! and I never even mentioned the company!.

Many thanks for your help Andre

Sole