vOps Default accounts
Web UI :
SSH-putty to appliance :
The UI logs. If any errors pop up in the UI (“Error on Server Side”) the details will be here. It also shows the details of login errors.
Update logs. Any failures to update the application will be displayed here.
Collector log. Shows all tasks running and the details of any tasks that fail. Shows fairly verbose information and rolls over quickly. There is not much histlry, but lots of details. This is one of the more frequently accessed logs for troubleshooting.
Collector log. Shows all tasks and their complete/fail status, but no details of any failures or warnings. As a result, rolls over infrequently and shows long-term behavior without much detail.
Does not exist in a directory. Generated at the time logs are gathered by script or UI. Can be seen in the generated archive only.
Log files: /usr/local/vkernel/log
Config files: /usr/local/vkernel/conf
Build files: /usr/local/vkernel/tools/ant
Important Configuration Files
Useful to determine the configuation of the database from the console window or SSH session. The file can be edited.
Contains the logging levels for each task. You may sometimes need to change the WARN level to DEBUG in order to get enough information to troubleshoot. Explicitly requested by dev. Changing this file incorrectly can cause the logs to expand out of control.
Initiates a script that assists in changing networking information. Usefull if a user does not have enough Linux knowledge to set the parameters.
Deletes all information in existing logs. Useful if a user makes a major change and wants to easily view the behavior from that point on without analyzing timestamps.
Allows external APIs (such as our own Hyper-V Collector) to connect to the internal postgresql database.
Removes any duplicate datapoints found in the database. Also corrects timestamps that are somehow wrong (usually through NTP problems or other time changes). Sometimes good to run after data migrations or timezone shifts (tzselect.sh).
Saves the logs in an archive called logs.tar.bz2. Same contents as gathering them through the UI, but if a user cannot get to the UI this is a viable alternative.
Allows you to manually schedule tasks for the Collector. If you want to test the behavior of a certain task after making a change, you can execute this to avoid waiting for said task to run at its next interval.
Clears out the configured database connection information. If you go the UI after running this the first screen presented will be a prompt to configure a new database (postgres, mssql, or oracle).
Clears out the configured database but ALSO drops all of the tables on the postgresql database.
Creates a new default vkernel/vkernel user that a user can log in with in the UI. Great when people forget the passwords. Not applicable for ActiveDirectory. This is for local users only.
Restarts the four relevant VKernel services: tomcat, postgresql, vkernel_collector, and vkernel_monitor.
Sets the proxy information. This exists in the UI under Settings > General > Proxy, but some users need a proxy configured to even access the UI by LAN.
Creates a command line SQL session to the configured database. This is useful when a user has an external database configured but does not have access to the database without involving a DBA.
Guides the user through selecting the correct timezone (in case NTP doesn’t change it automatically).
Executes the updater. Similar to clicking the update button in the user interface. Very useful if the update is having problems and a user want to watch it as it runs.
Shows the current release version, build number, and schema version.