Testing Server Before Deployment

[TheLawyerMan]

Hey all,

What do you guys usually do to test a server before deploying it? Especially when that server was bought used on eBay and then upgraded with used parts?

I want to make sure that I don't have any issues with reliability.

 

Thanks.

[Electronics Wizardy]

Mostly just install oses, and run programs and see if you ahve any issues. Running memtest and a cpu stress is a good idea aswell. Normally if it doesn't have any issues in the first week its pretty good for me.

[Senzelian]

Nothing.

Might sound stupid, but the best test is the real world. You just gotta make sure that you have backups and can get a crashed service back up and running as quickly as you need it to.

[TheLawyerMan]

6 minutes ago, Electronics Wizardy said:

Mostly just install oses, and run programs and see if you ahve any issues. Running memtest and a cpu stress is a good idea aswell. Normally if it doesn't have any issues in the first week its pretty good for me.

Have you ever, by any chance, seen this?

[TheLawyerMan]

1 minute ago, Senzelian said:

Nothing.

Might sound stupid, but the best test is the real world. You just gotta make sure that you have backups and can get a crashed service back up and running as quickly as you need it to.

Of course, but I want to make sure that doesn't happen. Are you suggesting to "semi-deploy' it"?

[Senzelian]

8 minutes ago, ALLSTAR1JAC2899 said:

Of course, but I want to make sure that doesn't happen. Are you suggesting to "semi-deploy' it"?

You asked what I usually do to test a server before deploying it. And that's what I usually do: Nothing.  

 

But to answer your question: Yup, semi-deployment sounds like a good idea too, if we're talking about the same idea here. I guess what I am saying is: Get whatever you actually want to get running, running! You can test a server with all sorts of benchmarks and weird niche tests and at the end it will still crash or come up with some unexpected error. The only way you can make sure that it does what you want it to do, is to make it do what you want it to do.  

[TheLawyerMan]

3 minutes ago, Senzelian said:

You asked what I usually do to test a server before deploying it. And that's what I usually do: Nothing.  

 

But to answer your question: Yup, semi-deployment sounds like a good idea too, if we're talking about the same idea here. I guess what I am saying is: Get whatever you actually want to get running, running! You can test a server with all sorts of benchmarks and weird niche tests and at the end it will still crash or come up with some unexpected error. The only way you can make sure that it does what you want it to do, is to make it do want you want it to do.  

fair point, that is what I asked.

That is what I mean by "semi-deployment." Thanks!

[Electronics Wizardy]

14 minutes ago, ALLSTAR1JAC2899 said:

Have you ever, by any chance, seen this?

yup it works fine for wht is is, but normally I juse ust a linux live usb as I like the linux terminal.

 

Id just do that getting it ready for deployment, normally in this pahse it can fail and not hurt anything, and you will have tested enough stuff to find all the big issues.

[TheLawyerMan]

2 minutes ago, Electronics Wizardy said:

yup it works fine for wht is is, but normally I juse ust a linux live usb as I like the linux terminal.

 

Id just do that getting it ready for deployment, normally in this pahse it can fail and not hurt anything, and you will have tested enough stuff to find all the big issues.

thanks