Resolved: Issue in Server Data Center Post: 303029820

Sponsored Content

The Lounge What is on Your Mind? Resolved: Issue in Server Data Center Post 303029820 by Neo on Friday 1st of February 2019 08:04:22 AM

02-01-2019

Administrator

It's sad that server4you does not care to even talk to me to address these major issues.

Well, I was fair and gave server4you two full days to respond to my ticket about problems with their customer support. I offered to speak with their management and tech leads on the phone. They did not take me up on my offer.

Here is a summary of what I told server4you:

During this outage on your end, I discovered these things about server4you.

Your Power Panel is very slow. Clicking between tabs can take up to 10 seconds or more just to go from panel to panel. This should take milliseconds, not many seconds. You must upgrade this user panel system to faster hardware and networking.
Your team does not monitor your own data center network. It should NOT be up to the customer to notify via a ticket that your own network has a problem. It is easy to set up internal server and networking monitoring. Why on Earth do you not have basic customer network management in place?
Your PowerPower does not provide any network status or server status. This is terrible. Why are your customers like us blind to if the server is up and running? You could write the code to fix this in less than a single day (if really senior tech).
Your PowerPanel does not provide any view into the server or server network at all. Your HOT LINE person telling me to REBOOT is wrong. Why should we have to HARD REBOOT the server when the server is UP ... this is because SERVER4YOU does not provide basic status to customers and even your own support HOT LINE people . Your HOT LINE person told me the network was fine. He was wrong. I knew it was a network issue on your end (or was pretty sure).
Your HOT LINE person was arrogant in my view. Yes, of course I was not happy. The PowerPanel is terrible. It's slow and nearly unusable, 8 to 10 seconds to load pages. There is no status for the server or my server's network in the panel. This is awful customer service for a data center.

It's sad that server4you does not care to even talk to me to address these major issues with their customer support.

Neo

View Public Profile for Neo

Visit Neo's homepage!

Find all posts by Neo

6 More Discussions You Might Find Interesting

1. HP-UX

Need to set up a HP cluster system in a data center

What are the server requirements, Software requirements, Network requirements etc, Please help me.. as 'm new 'm unable to get things done @ my end alone. Please refrain from typing subjects completely in upper case letters to get more attention, ty.

2. Infrastructure Monitoring

Agent Installation Issue on Ops Center

Hi guys . While installing the agent on an asset Solaris system: root@system: /var/tmp/OC $ /opt/SUNWxvmoc/bin/agentadm configure -u root -p /var/tmp/OC/mypasswd -x 172.21.16.65 agentadm: Version 12.1.2.2161 launched with args: configure -u root -p /var/tmp/OC/mypasswd -x 172.21.16.65 Validating...

3. Solaris

[Resolved] Strange Issue with user logins

Ok got a strange one here. None of my user accounts are able to login into the system. When trying to ssh to the server i get the following. Could not chdir to home directory /home/<homedir>: Permission denied /bin/sh: Permission denied I checked the permissions on the home directory and even...

4. Shell Programming and Scripting

Failure rate of a node / Data center

Hi, Please, i have a history of the state of each node in my data center. an history about the failure of my cluster (UN: node up, DN: node down). Here is some lines of the history: 08:51:36 UN 127.0.0.1 08:51:36 UN 127.0.0.2 08:51:36 UN 127.0.0.3 08:53:50 DN 127.0.0.1 ...

5. What is on Your Mind?

Cut Over to New Data Center and Upgraded OS Done. :)

Three days ago we received an expected notice from our long time data center that they were going dark on Sept 12th. About one and a half hours ago, after three days of marathon work, I just cut over the unix.com to a new data center with a completely new OS and Ubuntu distribution.

6. What is on Your Mind?

OUTAGE: Data Center Problem Resolved.

There was a problem with our data center today, creating a site outage (server unreachable). That problem has been resolved. Basically, it seems to have been a socially engineered denial-of-service attack against UNIX.com; which I stopped as soon as I found out what the problem was. Total...

LEARN ABOUT SUNOS

in.talkd

in.talkd(1M)						  System Administration Commands					      in.talkd(1M)

NAME

       in.talkd, talkd - server for talk program

SYNOPSIS

       in.talkd

DESCRIPTION

       talkd is a server used by the talk(1) program.  It listens at the  UDP port indicated in the ``talk'' service description; see services(4).
       The actual conversation takes place on a  TCP connection that is established by negotiation between the two machines involved.

ATTRIBUTES

       See attributes(5) for descriptions of the following attributes:

       +-----------------------------+-----------------------------+
       |      ATTRIBUTE TYPE	     |	    ATTRIBUTE VALUE	   |
       +-----------------------------+-----------------------------+
       |Availability		     |SUNWrcmds 		   |
       +-----------------------------+-----------------------------+

SEE ALSO

       svcs(1), talk(1), inetadm(1M), inetd(1M), svcadm(1M), services(4), attributes(5), smf(5)

NOTES

       The protocol is architecture dependent.

       The in.talkd service is managed by the service management facility, smf(5), under the service identifier:

       svc:/network/talk

       Administrative actions on this service, such as enabling, disabling, or requesting restart, can be performed using svcadm(1M). Responsibil-
       ity for initiating and restarting this service is delegated to inetd(1M). Use inetadm(1M) to make configuration changes and to view config-
       uration information for this service. The service's status can be queried using the svcs(1) command.

SunOS 5.10							    31 Jul 2004 						      in.talkd(1M)