- Sostatus tech install#
- Sostatus tech password#
Sostatus tech install#
To retrieve the VCA password, install osmclient and run the following:
Sostatus tech password#
Lxc exec VCA - juju config lxc exec VCA - juju list-actions lxc exec VCA - juju show-action-status lxc exec VCA - juju show-action-output VCA password Service osm-ro restart Troubleshooting VCA VCA status lxc exec VCA - juju statusĬheck that juju account is in 'green' status in the UI RO can be restarted on the RO container at: In case it is not running, try to see the last logs at /var/log/osm/openmano.log Restarting RO Nov 02 16:50:21 RO-integration systemd: Started openmano server. └─550 python openmanod -c /etc/osm/openmanod.cfg -log-file=/var/log/osm/openmano.log Loaded: loaded (/etc/systemd/system/rvice disabled vendor preset: enabled)Īctive: active (running) since Wed 16:50:21 UTC 2s ago The status of the RO process can be checked by running the following command in the RO container as root: Lxc exec SO-ub - nohup sudo -b -H /usr/rift/rift-shell -r -i /usr/rift -a /usr/rift/.artifacts. Lxc restart SO-ub # Optional, Needed if there is an existing running instance of launchpad When SO hasn't been started as a service, please follow the following instructions to restart the SO When the SO has been started as a service (see SO status section above), use the following commands to restart the SO: Note: Restarting the SO also restarts the UI. To check if the SO is running as a service, run the following command: The SO now starts as a service, but earlier versions of the SO used to run SO as a process.
However, in case just the UI needs to be restarted, you can run the following command in the SO-ub container as root:. The UI is restarted when the SO module (launchpad) is restarted. In case the UI server process never started, you'll see a status saying "No forever processes running". In case the UI server process has issues, you won't see an uptime but will instead see a status "STOPPED" in that position. You should see a status similar to following with an uptime:ĭata: uid command script forever pid id logfile uptimeĭata: uivz /usr/bin/nodejs skyquake.js -enable-https -keyfile-path=/usr/rift/etc/ssl/current.key -certfile-path=/usr/rift/etc/ssl/current.cert 21071 21082 /root/.forever/forever.log 0:18:12:3.231. The status of the UI process can be checked by running the following command in the SO-ub container as root:. VCA logs Troubleshooting Troubleshooting UI UI status Log file and log level ( debug by default) can be set at file "/etc/osm/openmanod.cfg" on RO container Lxc file pull RO/var/log/osm/openmano.log. You can get it from the container to the OSM machine with: RO logs are at file "/var/log/osm/openmano.log" on the RO container. SO logs can be obtained on the SO-ub container at: usr/rift/usr/share/rw.ui/skyquake/out.logĬlient side UI logs can be obtained in the Developer Console in a browser. usr/rift/usr/share/rw.ui/skyquake/err.log The server-side UI logs can be obtained on the SO-ub container at: If the error you experienced is not there, you can troubleshoot the different components following the instructions in this section. Known errors are captured in our Technical FAQ. 2.4.4 Known error messages in the VCA and their solution. So far what I gathered after all the testing that was done, we think it has to do with SO Cache not refreshing or reading when customer status changes. I even created a Widget and Business Event to alert and send out an email when this happens. My client has 2021 R1- Build 21.106.0024 and I do have the GI that is provided on the the link above. There is a known issue and says it was fixed in Build 2021 R1 21.102.0070: All of the sudden I get a report that I have an issue in InItemPlan where the Hold field is True (t), while all other tables the status is False (f). So far, great… Customer is still on a Credit Status so the user goes and changes it to Active. The order changes to Status On Hold until a Prepayment is entered, then they enter a prepayment/payment and SO Status changes to Open. While the customer is set as Credit Hold and Terms are Prepay, users create a Sales Orders. Some of the Customers sometimes are with Status: Credit Hold. 
My Client has customers that are setup with Prepay Terms.
0 kommentar(er)
