the Everex m/c with PIAF latest build just went down abruptly

and for me, it failed yet another time. three times it has happened that i have found that there is no dial tone on the extensions, cannot SSH into the system and the only option is to do a hard physical restart. :cryin:

I've had this one happen before.
So far that one has gone away with my switch to TDM (Sangoma A200)
 
As well, I had an odd problem just now.
X 701 all of a sudden had garbled sound.
but X 702 was fine.

Attempts to get X701 back to normal (all failed).
1) restart Aastra 57i CT
2) unplug replug the Ethernet Connection.
3) unplugging my Plantronics headset.
4) amportal restart (after that, the phones wouldn't even answer).

What worked ..
1) Hard resetting the Everex PC.
 
My gPC2 also has locked up

I have the gPC2 with the SATA drive. It has 2 G RAM installed. Twice in the last few weeks, it has locked up with no access from the console (on a KVM) - blank screen. The system just will not respond. I am running the original 2-disk load with updates along the way. I have had the system since August. I do not have any cards in the system - no trunks connected at this time. I have Aastra phone, Polycom phone, and Cisco ATA-188 on the system.
All other systems on my network were working well. I have UPSs for each system and the DSL and switches.
Does anyone have a favorite RAM test freeware to try?
Maybe that will find the problem. I am getting ready to update to Ward's new 2-disk release but am patiently waiting on this.
Thanks
TomS
 
Everex Orgasmatron Problems.

Twice in the last few weeks, it has locked up with no access from the console (on a KVM) - blank screen. The system just will not respond.

My Everex crashes just like this.
Wednesday - crashed
Thursday - survived 200 calls.
Friday - needed 1 reboot.
Saturday - crashed.

I have a spare Everex which I am going to try to see if it is more reliable. But I think I need to get away from this Everex ASAP !
 
Similar

This thread seems to have similar issues to what is discussed in this thread
 
Last edited by a moderator:
If you've installed Munin, take a look at the stats and see if there's anything unusual. We have three of these boxes running with no problems so there is nothing inherently wrong with the machines. After all, they use industry-standard components that are found in most other PCs.

I did have one of our units that always seemed to be pegging the CPU even for the simplest tasks. I restored that system from a Mondo backup and haven't had the problem since. Unlike some operating systems, Linux apparently has "issues" if it happens to stumble upon a bad sector on the hard disk. Sometimes a complete backup and restore will fix it because you're blocking out bad sectors again. Just a few ideas. Good luck.
 
There is an install-munin script included in PiaF

Joe
 
What I find interesting is I began experiencing what have become typically weekly lockups (sometimes less, sometimes more), that have occurred only at night. This machine (original gPC) has been in use for the better part of eight months now, and only began doing this over the past month or so. Which coincidentally was about the time I updated to 1.4.21.2 and the freePBX 2.5 beta.

I use two other original gPC's in my household as well. One is used as a firewall (endian), another has WinXP installed. Neither of these machines have had any lockup issues. I admit the firewall never breaks a sweat, but the WinXP machine runs discrete PCI video and I have kids that push it pretty hard. The WinXP box has forgotten it had a keyboard a couple of times, but neither have had any lockup issues (as in zero) in the six months+ they've been in use.
 
My daily crashes solved

If you were like me and followed the Orgasmatron tutorials to the detail you may have purchased the wrong memory from 1stchoicememory.com. The link in the tutorials sends you to the ram specific to the gPC....NOT....the gPC2.

I followed the link and purchased without noticing that it wasn't the correct RAM for the gPC2.

As soon as I pulled the stick of RAM out that wasn't meant for the gPC2 I solved all my problems. So many of the descriptions in this thread match what was happening to my system.

A quick MemTest86+ with both RAM sticks in showed errors....maybe 25 minutes of testing max and the errors were obvious. The RAM when tested with just one stick at a time in the system came up clean with no errors even after all night of testing.

I hope this helps....please post if you did the same thing as I did....it will make me feel less stupid.:banghead:

Viva PBX in a flash!!
 
To re-enforce what CJ6814 posted above, I just had an original gPC flake out due to this memory issue. It had two identical matched 1GB sticks and worked flawlessly for the last 10 months. Not sure what was the tipping point, nothing changed on the machines end, but it began locking up and then hang during the boot process. Strangely, it would boot fine using a live CD (first Spinrite so I could check the HD, then Ubuntu), so seems this problem would only occur when the memory was trying to access the HD- in bigger chunks than Spinrite's sector-by-sector access . Removing one of the memory boards (didn't matter which) solved the problem.

I'm not sure if there are Motherboard/Bios updates available, but it would seem that this would offer the best chance for a fix.
 
Glad I remembered this thread. Abrupt crashes becoming more frequent here on the GPC2, and I had the 1stchoicememory per the article.

I've pulled the extra ram. Let's see how it goes. Meanwhile I'll dig into logs and try to learn what a munin is. :)



I wonder if this machine is just sensitive to mismatched RAM in dual channel mode.
 
All of these machines were sensitive to mismatched RAM. Once you use compatible RAM, all the problems go away. :wink5:
 
/happy

My Orgasmatron II (only one stick of RAM) has been working great ! Not one hardware glitch :)

/very happy.
 
i may have discovered the issue here.

last night we had a one minute power failure. and this morning, the machine had the mysterious everything down situation. when i physically looked at the machine, the led was off and all i had to do was to press the feather-touch power button on the box.

it appears that the server is set to not start after a power failure. need to make a change in the BIOS? will try that and report in any case.
 
I think at least my issue on this mysterious "going down" of the system was as simple as 5 second long power failures. I changed the bios setting and the machine has not had failure as described above - although it did get restarted in a recent storm.

i do not see a way of marking a thread solved, otherwise I would mark this solved.
 

Members online

No members online now.

Forum statistics

Threads
26,687
Messages
174,411
Members
20,257
Latest member
Dempan
Get 3CX - Absolutely Free!

Link up your team and customers Phone System Live Chat Video Conferencing

Hosted or Self-managed. Up to 10 users free forever. No credit card. Try risk free.

3CX
A 3CX Account with that email already exists. You will be redirected to the Customer Portal to sign in or reset your password if you've forgotten it.
Back
Top