Sip Server - full disc with qsp files

[eduardosaito]

Hi everyone,

We had some issues with Sip Server, after the disk got full with qsp files and the disk didnīt have enough space for more. (192k free and each qsp had 270kB)

While we didnīt solve the message server issue with the database, we removed the "network" value from the log section in sip server options.

Didnīt find anything related to this issue in Sip Server guides.

Has anyone had this issue before? is this the expected behavior when the disk is full and sip server canīt create another qsp file ?

Thanks in advance!

[cavagnaro]

Well if HD is full how you expect to new files be created?

From Genesys:

[quote]
.qsp files are created when an application is configured for network logging but cannot connect to Message Server
To ensure the log information is not lost; a local .qsp file is created
Once the connection between the application and the Message Server is resumed, the qsp files will be removed and sent to Message Server
If the application has been restarted, it will not clear qsp files written by the previous instance
[/quote]

This is part of Common TServer components level
Check T-Server Deployment Guide: Common Configuration Options

[hsujdik]

I think what he meant is if anyone else had "issues" with SIP Server after the disk got full (although issues had not been defined). Did I get it right?

Well, so far I haven't had a SIP Server running on an operating system that had the partition where SIP Server is located full... but had this bad luck with other applications (MCP) and yes, they usually crashed when this happened.

[eduardosaito]

Hey guys,

the issue was DN's getting unregistered and agents logged out. The application didnīt stop, neither got switched over ... it kept as primary but stopped working properly.

I know the files wouldnīt be created anymore but just wanted to know if the issues mentioned are expected when the disk gets full with those files. I thought that it could just alarm on sci and stop creating new files (or maybe replace the oldest ones like the regular log files when you set the segment and expire parameters.

[cavagnaro]

Well I have seen weird behaviour too when a HD fills up, you can't assure behaviour, just that. No application is designed to work on those extreme out of normal environments. If you want an alarm when the problem is there makes no sense, why not better monitor and alarm via SNMP or other ways when HD has only 10% free space for example?
Don't try to Genesys do everything for your environment, OS and HW are another layer, talk to those guys about that and how to avoid it on the future

[hsujdik]

[quote author=eduardosaito link=topic=9370.msg42316#msg42316 date=1455749132]
I thought that it could just alarm on sci
[/quote]

Adding to what cavagnaro already said, in your case an alarm also would not work. Those type of alarms rely on sending LogLib messages to Message Server which would in turn alert Solution Control Server to generate the alarm. Since your communication with Message Server was already broken, the alarm would not be triggered.