PI Buffer Subsystem health alerts

Failed to create API shared memory buffer

PI Buffer Subsystem cannot create the API shared memory buffer. As a result, PI API data is not buffered for this server.

Check the message log for possible causes of this error. Two common causes are:

• One or more interfaces were still accessing the shared memory buffer from a previous session when pibufss was started.

• Stop the interface (or interfaces) and wait approximately 1 minute. Then view the Buffering Manager dashboard. When the message has disappeared, restart the interfaces.

• If you don't know which interface is at fault, stop and restart all interfaces that write to the target Data Archive server.

• PI Buffer Subsystem does not have sufficient permissions to create the shared memory buffer.

• Review the permissions for the account the PI Buffer Subsystem service uses to log on, and modify them if needed. For more information, see PI Buffer Subsystem and service logon accounts.

Failed to load configuration file (pibufcfg.xml)

PI Buffer Subsystem cannot find pibufcfg.xml or the file is corrupted. PI Buffer Subsystem will continue to buffer data using default configuration settings.

Run Buffering Manager and click the Settings link. If needed, change settings to implement the expected configuration. Click Save. This recreates the configuration file and should resolve the issue after 1 minute.

User disabled data sending (-bc stop command)

Queuing data but not sending it to the server. This can occur after you change the buffer location by setting Queue path in Buffering Manager, or when a user intentionally issues the pibufss -bc stop command.

If you used Buffering Manager to change the buffer location (Queue path), status should return to normal in a few minutes when the change is completed.

If a user issued the pibufss -bc stop command, then to resume buffering, open a command window, navigate to the \PIPC\bin folder and type:

pibufss -bc start

If prompted, specify the server receiving buffered data, the buffer session number, or both for the affected server.

User disabled data queuing (-bc dismount command)

Neither queuing data nor sending it to the server. All incoming data for this server is lost. This can occur after you change the buffer location by setting Queue path in Buffering Manager, or when a user intentionally issues the pibufss -bc dismount command.

If you used Buffering Manager to change the buffer location (Queue path), status should return to normal in a few minutes when the change is completed.

If a user issued the pibufss -bc dismount command, then to resume buffering, open a command window, navigate to the \PIPC\bin folder and type:

pibufss -bc start

If prompted, specify the server receiving buffered data, the buffer session number, or both for the affected server

The configured queue path is not yet in effect

The buffer location has been changed in configuration, but PI Buffer Subsystem has not applied the change yet.

If you used Buffering Manager to change the buffer location (Queue path), status should return to normal in a few minutes when the change is completed. If the issue persists, check the message log for the root cause of the problem. Some common causes are:

• The disk is full. Increase the disk space or use a different buffer location.

• PI Buffer Subsystem does not have sufficient permissions to write to the new location. Review the permissions for the buffer location (Queue path in Buffering Settings), and modify them if needed. For more information, see Operating system permissions for buffering.

Failed read from or write to data path ($ProgramData \ OSIsoft \ Buffering)

When this happens, PI Buffer Subsystem cannot buffer or fan data.

Add the required permission to the account the PI Buffer Subsystem service uses to log on, then restart the service. For more information, see Operating system permissions for buffering.

Failed load pibufss.dat (or pibufmem.dat in upgrade case)

This file was corrupted when PI Buffer Subsystem was last started. As a result, PI Buffer Subsystem no longer has the list of servers to which it was sending data before it was last shut down.

If there was no buffered data when pibufss was last shut down, you can ignore this message and clear the issue. To do this, open a command window, navigate to the \PIPC\bin folder and type:

pibufss -health -clear 5

If there was buffered data, or if you are not sure, contact customer support.

There are configuration errors

This message indicates a configuration problem not covered by other messages. For example, it might indicate a setting that is not within the permitted range.

This message is unlikely if you use Buffering Manager to configure buffering.

If there was no buffered data when pibufss was last shut down, you can ignore this message and clear the issue. To do this, open a command window, navigate to the \PIPC\bin folder and type:

pibufss -health -clear 5

If there was buffered data, or if you are not sure, contact customer support.

Received error(s) when posted to certain point(s)

PI Buffer Subsystem received errors when posting to certain points.

To check error details, open a command window, navigate to the \PIPC\bin folder and type:

pibufss -cfg

For example, you might see a message like this:

[-11473] There are configuration errors: collective1\memberA: retryRate out of range.

Then use Buffering Manager to adjust the configuration accordingly. You may need to contact customer support.

Corrupted queue has been detected and moved, the old queue(s) can be found under the configured queue path

When PI Buffer Subsystem started, it detected queue corruption and moved the old queue files to a separate folder within the Queue path. The folder structure for corrupted queue files is:

\autoreset_corruptedQueues\ logical_server_name\ physical_server_name\ current_timestamp

Contact customer support.

Error reading from the buffer queue

PI Buffer Subsystem is queuing data, but is not able to read data out of the queue to send it to the server.

Contact customer support.

Error writing to the buffer queue

PI Buffer Subsystem is not writing data to the queue. All incoming data for this server is lost.

Check the message log for the reason. If the disk is full, try to make room or use Buffering Manager to change the buffer location (Queue path).

If that does not resolve the issue, or if the message log indicates a different reason, contact customer support.

Low buffer queue capacity (Critical)

The disk containing the buffer queue is full. All incoming data for the affected server(s) is lost.

If PI Buffer Subsystem is queuing data because the Data Archive server is down or connection to the server is lost, check whether you can bring up the server or reestablish the connection.

If you cannot connect to the server right away, options include:

• Delete or move other files on the disk to make room in the buffer queue location.

• Use Buffering Manager to change the buffer location (Queue path) to a disk with more available space. In Buffering Manager, click the Settings link. In the Buffering Settings window, select the affected server, change its Queue path, and click Save.

Low buffer queue capacity (Error)

The disk containing the buffer queue is almost full. PI Buffer Subsystem can continue to queue data for approximately 24 more hours.

Same as Low buffer queue capacity (Critical), except that you have approximately 24 hours to resolve the problem before data loss occurs.

Note: Changing the buffer location can cause temporary data loss.

Low buffer queue capacity (Warning)

The disk containing the buffer queue is low on space. PI Buffer Subsystem can continue to queue data for approximately 7 days.

Same as Low buffer queue capacity (Critical), except that you have approximately 7 days to resolve the problem before data loss occurs.

Note: Changing the buffer location can cause temporary data loss.

Queue path changed. Did not find queue(s) in the new location, may have lost data

The buffer location was changed, but the existing buffer queue files were not successfully moved to the new location.

Check the old buffer location. If it contains buffer queue files, contact customer support. The data in those files may need to be manually reprocessed.

Failed to initialize/load the buffer queue

PI Buffer Subsystem cannot create the buffer queue in the configured buffer location. All incoming data for the server is lost.

Check the message log for the root cause. Common causes are:

• PI Buffer Subsystem does not have sufficient permissions to create the file in the configured buffer location. For more information, see PI Buffer Subsystem and service logon accounts.

• There is not enough disk space in the configured buffer location for PI Buffer Subsystem to create buffer queues. Options include:

  • Delete or move other files on the disk to make room in the buffer queue location.

  • Use Buffering Manager to change the buffer location (Queue path) to a disk with more available space. In Buffering Manager, click the Settings link. In the Buffering Settings window, select the affected server, change its Queue path, and click Save.

Not connected to the server

Queuing data but not connected to Data Archive.

Check whether the server is available. If it is a connection problem, try to reestablish the connection.

No communication with PI Snapshot Subsystem. Not sending data

Queuing data and connected to Data Archive, but cannot send data. PI Snapshot Subsystem may be busy or stopped.

Check the status of PI Snapshot Subsystem on the target Data Archive server.