First off, thanks to the Giga Team for providing me with the opportunity to check on their free VPS offerings. Although, system security and administration is nothing new to me, having to exerce that Art on a live system within a virtual environment is indeed a brand new experience to me to say the least.
Now, i've spent sometime trying to configure this VPS of mine and for the time being I've still didn't add any service to it besides those already running out-of-the-box. The reason for this is that I did stumble with a rather unexpected issue concerning the system's time which is grossly inaccurate: ~5 hours in advance
Besides the problem of the out of sync system time inside the VPS, I also run into the problem of finding that Virtualizor isn't installed at all although I was given its login. Not sure how that occured. Is it a step that was skipped during the VPS creation or has it failed when it was run. From my logs, I couldn't detect any trace of it.
This issue however isn't critical as far as I'm concerned. I was planning to disactivate its service anyway. I'm more at ease with the manual administration of a system than with all those script-based GUIs.
Running the following systemd cmd to get the list of the services that fails at system satrtup:
I suspect that the first 2 failures are due to the OpenVZ environment... and hopefully without any impact on sytem stability. The last one I still didn't document it at this point.
Those are my two main feedback/heads-up that I have for the moment. And thanks for any assistance concerning the out-of-sync time issue.
Now, i've spent sometime trying to configure this VPS of mine and for the time being I've still didn't add any service to it besides those already running out-of-the-box. The reason for this is that I did stumble with a rather unexpected issue concerning the system's time which is grossly inaccurate: ~5 hours in advance
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>vzctl set VMID --capability sys_timen --setmode restart --save
Besides the problem of the out of sync system time inside the VPS, I also run into the problem of finding that Virtualizor isn't installed at all although I was given its login. Not sure how that occured. Is it a step that was skipped during the VPS creation or has it failed when it was run. From my logs, I couldn't detect any trace of it.
This issue however isn't critical as far as I'm concerned. I was planning to disactivate its service anyway. I'm more at ease with the manual administration of a system than with all those script-based GUIs.
Running the following systemd cmd to get the list of the services that fails at system satrtup:
PHP:
#systemctl --state=failed
UNIT?????????????????????????? LOAD?? ACTIVE SUB??? DESCRIPTION
systemd-sysctl.service???????? loaded failed failed Apply Kernel Variables
systemd-vconsole-setup.service loaded failed failed Setup Virtual Console
vzquota.service??????????????? loaded failed failed LSB: Start vzquota at the end of boot
LOAD?? = Reflects whether the unit definition was properly loaded.
ACTIVE = The high-level unit activation state, i.e. generalization of SUB.
SUB??? = The low-level unit activation state, values depend on unit type.
3 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.I suspect that the first 2 failures are due to the OpenVZ environment... and hopefully without any impact on sytem stability. The last one I still didn't document it at this point.
Those are my two main feedback/heads-up that I have for the moment. And thanks for any assistance concerning the out-of-sync time issue.
