ParStream log file rotate 20181107 firstname.lastname@example.org also at: TechZone
ParStream log files grow forever until out of disk space Applies to all ParStream (current) v6.0.1 and earlier (Kinetic EFM v1.6)
Use nohup and logrotate together.
First, use "nohup" to start the ParStream service and redirect the logging output to the STDIN of CAT instead of to the (default) I/O layer.
I start the ParStream like this instead:
su efmuser cd /opt/cisco/kinetic/ParStream-Data nohup /opt/cisco/kinetic/parstream/bin/parstream-server ps1 2>&1 </dev/null | cat >> /var/log/parstream/server.log &
Change these parameters for your environment, for this example, ParStream is executed with the service account "efmuser" the /conf directory with the parstream.ini file is located in /opt/cisco/kinetic/ParStream-Data/conf the database is named ps1 and the log file is written to /var/log/parstream/server.log
Next, set up the Linux logrotate utility to manage the ParStream log files. I named the file "kinetic_efm_parstream". Change this file to suit your environment then copy it to your ParStream node - place your logrotate script file in the directory “/etc/logrotate.d”. You should change the user and group on the first line, the example below uses "efmuser isu.users". In addition, you may have different retention needs, but the example below will compress logfiles that grow beyond 50MB (size) and keep the last 10 compressed files (rotate).
note: if this file is not owned by root after you copy it, you could change ownership like this: chown root:root /etc/logrotate.d/kinetic_efm_parstream
nohup is required here because logrotate cannot make the ParStream process release the file it is logging to. Since we want to keep ParStream database service running while logrotate cycles the log files, we need to change the way we start ParStream. With this nohup command line, ParStream will send the logging output to the STDIN of cat instead of the I/O layer, which instead will relay the log file messages to the I/O layer. Logrotate can rotate the log from cat without interrupting the ParStream logging process.
Q. Where can I find the Cisco Kinetic DemoKit Setup Guide?
A. Refer to the "Cisco Kinetic Demo Kit Guide" on Salesconnect (https://salesconnect.cisco.com/#/program/PAGE-10238 then under the "Demo Kit" tab)
Q. Where can I get support for the DemoKi...
Industrial customers are increasingly realizing the importance of digitization to compete and stay relevant in today's business environment. Any digitization efforts involve connecting thousands of sensors and devices to the network, extracting and proces...
This example shows ICPAM integration to VSM 7.12
Principal of operation:
SENSOR_CONNECTOR will connect to ICPAM & register the callback endpoint. Currently SENSOR_CONNECTOR is registering endpoint for all types of events available in ICPAM.
You have confirmed that EFM is running, and you can open a broker connection using port 8080 or 8443 from the EFM server. However, from an external broker, not hosted on the same machine, the connection is refused.
Is this is your fi...
EFM broker connection to upstream EFM server is failing. You have confirmed that the IP connectivity to the destination port number (tcp/443 by default) is open, yet the connection does not establish from the EFM broker to the EFM server.