sys-unconfig

[Kyndig]

:: while running through unknown new commands hits the sys-unconfig button :: D'oh! ::puts in reboot request :: dum dee dum dee dumm

[Kyndig]

I posted 3 threads in reply to this one here. They have all been removed by board moderators. I am disgusted by this company, disgusted by their lack of support, and overall highly unimpressed. They filter out competitors with this system, and claim to be developed by the developer of RackSpace. Let me tell you gurus something, if you folks were developed by Rackspace, I am leaving them after 4 years of being a client just in time. I have been treated poorly as a client. There have been zero emails, phone calls or contacts in regards to my server issue that is now 6 hours old. I demand a response to my trouble ticket. Period.

[JoshPet]

a) your posts haven't made much sense

b) you've cross posted stuff - that's probably why they remove stuff.

c) this is the off-topic forum. A forum specific to your OS might be more appropriate. ;)

d) this is a user to user support forum. Nobody here can help you with a reboot request. You need to use the rapid reboot system or open a trouble ticket.

RackSpace is Managed..... ServerBeach is UNManaged.

"while running through unknown new commands hits the sys-unconfig button " :poke:
This is not a managed/hand holding provider. It's unmanaged. You're responsible for what you break. ;) If you need assistance, a ticket takes time depending on how many other tickets they have and the urgency of it.

If it's a production server, and you don't know what you're doing and you hose it up - then that's a risk you take. ;)
You seem to have read nothing here - other than come here to complain. If you are new to managing a server, there are lots of "how tos" and other posts here to help you.

:flush:

</rant off>

[QT]

Originally posted by Kyndig
I posted 3 threads in reply to this one here. They have all been removed by board moderators.

Your posts have been removed due to you purposely avoiding censored words in order to bad mouth a company. You are more than welcome to post and rant all you'd like, but deliberately posting around censorship just to bad mouth will not be tolerated.

[Kyndig]

Before you folks go teaming up on the FNG here. I'll be cancelling my boxes on Monday. Probably will get a song and dance as to why I am out $218.00 , but that is now to be expected from the type of service I've received here. If they do in the end surprise me and provide even a pro-rated return, I'll make sure to post back.

I appreciate your concern on the matter. Yet since you have decided to make your assumptions, let me reply to them in kind:

Originally posted by JoshPet
[B]a) your posts haven't made much sense

This is irrelevant.


b) you've cross posted stuff - that's probably why they remove stuff.

Initially I had wanted to REPLY to this thread, yet hit the POST NEW instead. Yet the new thread was relevant to the subject.


c) this is the off-topic forum. A forum specific to your OS might be more appropriate. ;)

This links to b. My first post was about me being a ninny and executing a command which had adverse affects on my server.


d) this is a user to user support forum. Nobody here can help you with a reboot request. You need to use the rapid reboot system or open a trouble ticket.

The deleted thread explained the problem. I had rebooted with the rapid reboot. It took 45 minutes almost to the second for it to state my server was ONLINE. My server did not ever come back online. I opened two trouble tickets, and neither appeared in my TICKET CONSOLE. After the 3rd trouble ticket however, it showed up in my ticket console.


RackSpace is Managed..... ServerBeach is UNManaged.

This is no excuse. I am not seeking a hand hold. I am asking for either 1: a fix within an hour, or 2: a full OS reinstall. I received neither..nor a response.


"while running through unknown new commands hits the sys-unconfig button " :poke:
This is not a managed/hand holding provider. It's unmanaged. You're responsible for what you break. ;) If you need assistance, a ticket takes time depending on how many other tickets they have and the urgency of it.

You are making poor excuses here. While I continue to expand on my understanding of administrations, my education and years of experience does go a long ways in stating that I do know somewhat of what I am doing.
I simply have never typed in: sys-unconfig before. Albeit, a quick: man sys-unconfig had me cursing up a storm a moment later, but that is a moot point.


If it's a production server, and you don't know what you're doing and you hose it up - then that's a risk you take. ;)


21 servers, 2 of which are hosted here and six years of network administrations. What can I say, other than: oops. I want better response time. This isn't about me hosing a box. I am extremely upset about the lack of response time. I have receiving _nothing_ from these people in six hours.


You seem to have read nothing here - other than come here to complain. If you are new to managing a server, there are lots of "how tos" and other posts here to help you.

I started with HOW TO's, and still refer to them this day. My favorite manual is HTML 4.0 for dummies. Yet I am not a newbie to server management. After stripping all the irrelevant Xserver GUI junk on the Fedora install they gave me, I updated the box with this "yum" thing that RH came up with. Rebuilt apache webserver with proper suexec variable, compiled/installed bind (chroot), and a handfull of little things here/there. I was trying to figure out why my "setup" command wasn't showing system services. I hit: sys (tab tab) to see what commands started with 'sys'..and saw sys-unconfig ..and thought "Hmm..that's new" ..Oops.


:flush:


Uh huh, that's pretty much what I though about your post.

[Kyndig]

Originally posted by QT
Your posts have been removed due to you purposely avoiding censored words in order to bad mouth a company. You are more than welcome to post and rant all you'd like, but deliberately posting around censorship just to bad mouth will not be tolerated.

To "bad mouth" a company? No ma'am. If these boards could yell, I would be screaming at the top of my lungs right about now. Therefore, you are stating that if I were to mention a companies name and not "bad mouth" this company, it would not be censored or deleted? I find that extremely difficult to believer after what I have been a part of here. How about you folks give me my money back and we'll call it a love story.

[QT]

Originally posted by Kyndig

I simply have never typed in: sys-unconfig before. Albeit, a quick: man sys-unconfig had me cursing up a storm a moment later, but that is a moot point.
I hit: sys (tab tab) to see what commands started with 'sys'..and saw sys-unconfig ..and thought "Hmm..that's new" ..Oops.

Well, at least you've learned the meaning of sys-unconfig now. :emlaugh:

I know the issue is not funny, but your 'cursing up a storm' made me giggle. ;)

I do hope that things wind up a little brighter in the end for you. :)

[QT]

Originally posted by Kyndig
To "bad mouth" a company? No ma'am. If these boards could yell, I would be screaming at the top of my lungs right about now. Therefore, you are stating that if I were to mention a companies name and not "bad mouth" this company, it would not be censored or deleted? I find that extremely difficult to believer after what I have been a part of here. How about you folks give me my money back and we'll call it a love story.

I'm willing to bet that these boards could yell a thousand stories. If they didn't have some issues here and there, there would definitely be something to be suspicious about.

Please do not mis-interpret my post and let me be clear in saying that I am _not_ an employee of ServerBeach. Your post was removed due to deliberately avoiding censorship..nothing more, nothing less.

Let's face it, the bashing, the bad-mouthing, the promoting other companies in one providers forum is really not necessary, is it? I really do understand your frustrations, as I see many people becoming frustrated recently and a public forum is a great place to vent. But I am also fully aware that this is not the norm for ServerBeach. I've had servers here from day one (back in Sept/02) and they truly have came a long way since then. There has been some issues with their recent migration and I believe they're slowly recovering from them.
I'll say again, that this is not the norm for them.

I hope your issues are resolved soon for you.

[Kyndig]

Originally posted by QT
[B]Well, at least you've learned the meaning of sys-unconfig now. :emlaugh:

*ROFLMAO!!*

Now that I can deal with. *smirk* Don't flame me for flaming folks. I'm venting at my own stupidity here. I fully understand "unmanaged". In fact, I told Rackspace I was closing my last box with them because they charged too much and I simply did not require that level of support. In all my boxes, I can count on one hand the trouble ticket I've opened. I just don't have any issues..gimme a box and a good network, and that's all I need. But if I "halted" a system..then a reboot _should_ work.

Care fer me own hypothesis?:
While securing the box, I ran across a daemon 'sbadm' (or somethin close to it ) operating. I removed this daemon and the ssh_config hack it had attached to it. I fully reinstalled SSH to ensure there were no 'remnants' of it poking around. I believe ServerBeach uses this to control their remote reboot or monitoring system? Probably so. Lemme say BaAaDDdd juju there.


I know the issue is not funny, but your 'cursing up a storm' made me giggle. ;)

Heh, good thing I'm being amiable. Otherwise you'd have just croaked from laughter by this point.


I do hope that things wind up a little brighter in the end for you. :)
Ayup, thankya kindly.

[QT]

Re: sbadm -

http://serverbeach.com/forums/showthread.php?s=&threadid=1820&highlight=sbadm

Originally posted by knightfoo
The sbadm daemon only accepts key-based logins from a couple of our administrative servers. The port is filtered so no one can access it from outside of our network, or even from different subnets on our network. It does allow root logins so support can perform tasks such as password resets without having to take a walk. You can disable, but it may slow down support in some cases and there may be future support offerings that depend on it. Since it runs on an odd port which is filtered and only accepts key-based logins, I don't consider it much of a security risk .. if there was ever an SSHD exploit, you'll probably be exploited via port 22 first.

-knightfoo

:D

[Kyndig]

It's back online now for 26 minutes. I just logged in. Time to get back online:
5 hours 23 minutes

Clients received in the 3 hours I moved the domain off that box: 0

Potential: who knows...

rm -rf /

[QT]

Good to see you're back up and running. :)