Hello!
I mirgated yesterday a Promox 1.9 Server to latest 2.x. Migration - stop VM, backup and restoring the VM on the new server.
Works fine. During the migration of an addional UNIX user for further purpose was created. No use/login of the this uset a this time. But this user exists also on the old server.
And now the strange thing - starting a certain CT, number 113 on the GUI as root@pam start all java VMs ot the CT in the context the addional user. All other CT programs of all other CTs run as root.
HTOP shows - xxx is the user
Very strange behaviour.
With best greetings
Peter
I mirgated yesterday a Promox 1.9 Server to latest 2.x. Migration - stop VM, backup and restoring the VM on the new server.
Works fine. During the migration of an addional UNIX user for further purpose was created. No use/login of the this uset a this time. But this user exists also on the old server.
And now the strange thing - starting a certain CT, number 113 on the GUI as root@pam start all java VMs ot the CT in the context the addional user. All other CT programs of all other CTs run as root.
HTOP shows - xxx is the user
PHP:
134771 xxx 20 0 1711M 1022M 14780 S 0.0 4.2 0:00.00 /opt/atlassian/jira/jre//bin/java -Djava.util.logging.config.file=/opt/atlassian/jira/conf/logging.properties -XX:MaxPermSize=256m -Xms256m -Xmx768m -Djava.awt.headless=true
134774 xxx 20 0 1711M 1022M 14780 S 0.0 4.2 0:41.32 /opt/atlassian/jira/jre//bin/java -Djava.util.logging.config.file=/opt/atlassian/jira/conf/logging.properties -XX:MaxPermSize=256m -Xms256m -Xmx768m -Djava.awt.headless=true
134776 xxx 20 0 1711M 1022M 14780 S 0.0 4.2 0:00.74 /opt/atlassian/jira/jre//bin/java -Djava.util.logging.config.file=/opt/atlassian/jira/conf/logging.properties -XX:MaxPermSize=256m -Xms256m -Xmx768m -Djava.awt.headless=trueVery strange behaviour.
With best greetings
Peter