expedition first time use - Remediation help needed

Reply
Highlighted
L1 Bithead

expedition first time use - Remediation help needed

In a new installation of Expedition upon first login we had three issues to remediate:

 

1. The instructions for "Verify that the SQL_Log_bin flag in MariaDB is set to off" were clear enough.  So that was addressed successfully.

 

2. Insufficient instructions for "Verify that the Log_bin flag in MariaDB is set to off". 

A search did not come up with instances of log_bin:

 

root:/etc/mysql# grep -i log_bin `find /etc/mysql -type f`
/etc/mysql/my.cnf:skip-log_bin = /var/log/mysql/mariadb-bin
/etc/mysql/my.cnf:skip-log_bin_index = /var/log/mysql/mariadb-bin.index
root:/etc/mysql#

 

3. Insufficient instructions for "Verify the PanOrders agent is running to accept background jobs"

A look at services located panReadOrders, but no PanOrders

 

root:/etc/mysql# service --status-all | grep -i pan
[ - ] panReadOrders
root:/etc/mysql# service panReadOrders status
● panReadOrders.service - LSB: starts panReadOrders agent for Expedition
Loaded: loaded (/etc/init.d/panReadOrders; bad; vendor preset: enabled)
Active: active (running) since Fri 2020-02-21 08:57:37 PST; 3 days ago
Docs: man:systemd-sysv-generator(8)
Process: 40502 ExecStart=/etc/init.d/panReadOrders start (code=exited, status=0/SUCCESS)
Tasks: 2
Memory: 11.7M
CPU: 4.871s
CGroup: /system.slice/panReadOrders.service
├─40508 sudo -u www-data php /var/www/html/console/messaging/readOrders.php
└─40512 php /var/www/html/console/messaging/readOrders.php

Feb 21 08:57:27 asa2pan systemd[1]: Starting LSB: starts panReadOrders agent for Expedition...
Feb 21 08:57:37 asa2pan systemd[1]: Started LSB: starts panReadOrders agent for Expedition.
Feb 21 08:57:37 asa2pan sudo[40508]: root : TTY=unknown ; PWD=/ ; USER=www-data ; COMMAND=/usr/bin/php /var/www/html/console
Feb 21 08:57:37 asa2pan sudo[40508]: pam_unix(sudo:session): session opened for user www-data by (uid=0)
root:/etc/mysql#

 

A bit more checking revealed a script:

 

root:/tmp# find / -print > filelist
root:/tmp# grep -i panorder filelist
/var/www/html/libs/PaloAltoNetworks/HealthCheck/PanOrdersAgentCheck.php
root:/tmp#

 

No change in symptoms after

 

root@asa2pan:/tmp# service panReadOrders restart

 

or


root@asa2pan:/tmp# service panReadOrders stop
root@asa2pan:/tmp# service panReadOrders start

 

Suggestions on how to overcome these are welcome.  Thanks.

Highlighted
L1 Bithead

After reading the discussion a bit more, found a reference to a button in the user interface.  Located the "RESTART" button  in the Dashboard for PanReadOrders and that issue is now resolved.

 

There is still that MariaDB log_bin issue.

 

Thanks.

Highlighted
L1 Bithead

Restarting the mysql and apache2 services in that order seems to have resolved the "log_bin" issue.

 

Apologies for the wasted bandwidth.

Highlighted
L0 Member

That worked for me too:

 

sudo service mysql restart

sudo service apache2 restart

Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the Live Community as a whole!

The Live Community thanks you for your participation!