SOLVED PBX Keeps crashing

[Starburst]

1&1 must have the WMware stuff in theirs, their monitoring is working.
Otherwise their images are almost less than the minimal than at Vultr.

Weird, because I know images are available for hosts.
But every host so far, has been different than just the "Minimal Install".

To create a snapshot of a server at 1&1, they want it stopped first for some weird reason.

We will see what happens tonight.

 

[Starburst]

Well crap, no modifications other than changing the SSH port #, and it still locked at 11:30pm ET.
@wardmundy

 

[wardmundy]

Well crap, no modifications other than changing the SSH port #, and it still locked at 11:30pm ET.
@wardmundy

I set up two systems on our VMware platform yesterday morning, and they’re still working fine today. So maybe it’s a 1&1 issue with their image. Our providers all work fine starting at $2 a month. Life is too short. wiki.incrediblepbx.com

 

[Starburst]

I set up two systems on our VMware platform yesterday morning, and they’re still working fine today. So maybe it’s a 1&1 issue with their image. Our providers all work fine starting at $2 a month. Life is too short. wiki.incrediblepbx.com

Could be.
I'm going to call them today.

The server time is set to Zulu time, so when the server went down it thought it was 0430.

The only thing it might be is a cron job running, and hosing the box.

But my CentOS box there isn't having any problems at all.

 

[wardmundy]

Might wanna stick with CentOS or move.

 

[Starburst]

Might wanna stick with CentOS or move.

Starting up another Debian 10 on a KVM system, will run them side by side.

While I was in the VPS it crashed at 1141, called 1&1 and their sys admin looked thru the crons, and their VMWare logs and didn't see anything either.
But now it really looks like a cron running twice a day at around 1130 and 2330. :/

Will see what happens tonight.

 

[Starburst]

@wardmundy

1&1 VPS locked up @ 2348 (0448 UTC server time)
Vultr VPS is OK.

Both are the same setup.

So the 1&1 VPS is locking up almost exactly the same time every 12 hours.

 

[krzykat]

Many years ago I had a similar sort of issue and it was due to the server setup on the cloud provider I was using. I switched across to Vultr and the problem disappeared.

Sounds like you are experiencing the issue I was commenting on. I ended up creating a cron job before I threw in the towel and just went to Vultr.

 

[dhoppy]

Is 1&1 that much cheaper than Vultr that it is worth the amount of time you've spent on this issue?

 

[Starburst]

Is 1&1 that much cheaper than Vultr that it is worth the amount of time you've spent on this issue?

$5/month for 2 VCPU & 2GB RAM, 400Mbps port.

Trying to not have all my eggs in 1 basket.

Another vendor just failed all together.

 

[kenn10]

Ditch 1&1 for VOIP. There are a lot of proven cloud services for less than $5/month. Some for $20 or @25/year. Not worth the wasted effort with 1&1. Hotlineservers is my new favorite.

 

[wardmundy]

@Starburst: Hate to say it but you've experienced more problems and issues setting up a single Incredible PBX server reliably than anyone I can remember... ever. IF there were actual issues with the setup process as designed, these forums would be full of posts from other users. They're not.

Many of us are willing to work with anyone to work out issues with installs, but those are precious resources that need to be spread across the entire community. You are fast approaching a threshold where you're probably going to have to chase some of these gremlins yourself without consuming a huge proportion of the support resources of the community.

 

[Eliad]

@Starburst: Hate to say it but you've experienced more problems and issues setting up a single Incredible PBX server reliably than anyone I can remember... ever. IF there were actual issues with the setup process as designed, these forums would be full of posts from other users. They're not.

Many of us are willing to work with anyone to work out issues with installs, but those are precious resources that need to be spread across the entire community. You are fast approaching a threshold where you're probably going to have to chase some of these gremlins yourself without consuming a huge proportion of the support resources of the community.

Indeed, 1&1 is not worth the effort for the few pennies you save. If you want good reliability just spend few more pennies on Vultr or DigitalOcean and you wont have this problems.

 

[jaminmc]

@Starburst Did you try the clean install from the NetBoot that I posted in https://www.voip-info.org/forum/threads/pbx-keeps-crashing.25330/post-154696 on 1&1?

Also, did you only try Debian, or did you try Ubuntu? I’d be interested in seeing if y’all be is better than the other on VMware.

I wonder then if it still crashes, if maybe you could try uninstalling open-vm-tools to see if that makes any difference.

 

[Starburst]

@Starburst: Hate to say it but you've experienced more problems and issues setting up a single Incredible PBX server reliably than anyone I can remember... ever. IF there were actual issues with the setup process as designed, these forums would be full of posts from other users. They're not.

Many of us are willing to work with anyone to work out issues with installs, but those are precious resources that need to be spread across the entire community. You are fast approaching a threshold where you're probably going to have to chase some of these gremlins yourself without consuming a huge proportion of the support resources of the community.

I know, and I appreciate all the help.
I'll just work on these systems myself.

It seems like if something can go wrong with what I'm trying to do, it will...

 

[dallas]

I know, and I appreciate all the help.
I'll just work on these systems myself.

It seems like if something can go wrong with what I'm trying to do, it will...

Don't get too disheartened... Learn to read log files and ask Google about any errors you find. It's the quickest way to find what's going wrong and it's a skill you will use often.
As @wardmundy says many here are willing to help but we like to see you make an effort too.

 

[Starburst]

@Starburst: Hate to say it but you've experienced more problems and issues setting up a single Incredible PBX server reliably than anyone I can remember... ever. IF there were actual issues with the setup process as designed, these forums would be full of posts from other users. They're not.

Many of us are willing to work with anyone to work out issues with installs, but those are precious resources that need to be spread across the entire community. You are fast approaching a threshold where you're probably going to have to chase some of these gremlins yourself without consuming a huge proportion of the support resources of the community.

Don't get too disheartened... Learn to read log files and ask Google about any errors you find. It's the quickest way to find what's going wrong and it's a skill you will use often.
As @wardmundy says many here are willing to help but we like to see you make an effort too.

Well there was this one time today at band camp...