Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

MiVB 9.x - EVM "System is full, try again later"

Status
Not open for further replies.

AH64Armament

Vendor
Sep 5, 2008
290
US
I ran in to this issue with one customer last March, and again today... with both that same customer and another.

In March, I spoke to Mitel Support and they suspected that the system had a bad drive, even though there wasn't any other indication of a failing drive.
At the time, there was an upgrade pending; so I applied it and the problem cleared.

This morning, we had 2 sites call in with this problem. The same one, and another.

Since my notes indicated that an upgrade should be done, that's what I suggested we do... but I researched the issue on MOL.

Document ID SO7085 indicates that they have found the issue and have no idea why this is happening.
The ownership of the files in the /vmail folder has changed from "voiceadmin" to root.

There's a command to fix this. Due to my agreement with Mitel, I cannot publish it here. But if you have access to MOL, you can search the KMS for the document number or the error.

There's other symptoms listed, but the one that I've now seen 3 times is "System is full".

Luckily most of our sites are running MiCollab with NuPoint so this hasn't affected many sites.
 
article is SO7185

To check the ownership use the following command at the shell # ls -l -R /vmail
There should be a large list of output like the following: drwxr-xr-x. 5 voiceadmin voicegrp 4096 Dec 15 2021 c

in the example output “voiceadmin” is the user ownership and “voicegrp” is the group ownership.
In the list, all the user ownership need to be “voiceadmin”

There may be some group ownership as “voiceadmin” and some as “voicegrp” This is OK

If there are any user ownership set to “root” you will have the problem.

Resolution
Issue the following command to fix the ownership # chown -R voiceadmin:voicegrp /vmail

If I never did anything I'd never done before , I'd never do anything.....

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top