Skip to main content

VMWare and time syncronization

I have an Ubuntu server with vmware-server running three other linux guests and, except, for time syncronization it runs quite smooth.
Today I eventually found some time to devote to this long-standing issue and I have applied this solution. It should keep behind the time in the guests so that the vmware-tools can update it.
On my machine I have a 3.2Ghz Pentium 4 cpu so I have set
host.cpukHz="3202000"
a bit higher to compensate for the higher frequency. Let's see how it works...

UPDATE: after two days the guests are still two hours ahead, so I decided to go for the easy route and set up a cronjob every two hours.

UPDATE 2: since time is not handled correctly also the cron job approach does not work.

Comments

Popular posts from this blog

Indexing Apache access logs with ELK (Elasticsearch+Logstash+Kibana)

Who said that grepping Apache logs has to be boring?

The truth is that, as Enteprise applications move to the browser too, Apache access logs are a gold mine, it does not matter what your role is: developer, support or sysadmin. If you are not mining them you are most likely missing out a ton of information and, probably, making the wrong decisions.
ELK (Elasticsearch, Logstash, Kibana) is a terrific, Open Source stack for visually analyzing Apache (or nginx) logs (but also any other timestamped data).

From 0 to ZFS replication in 5m with syncoid

The ZFS filesystem has many features that once you try them you can never go back. One of the lesser known is probably the support for replicating a zfs filesystem by sending the changes over the network with zfs send/receive.
Technically the filesystem changes don't even need to be sent over a network: you could as well dump them on a removable disk, then receive  from the same removable disk.

Detect missed executions with OpenNMS

Everyone knows that OpenNMS is a powerful monitoring solution, but not everyone knows that since version 1.10 circa it embeds the Drools rule processing engine. Drools programs can then be used to extend the event handling logic in new and powerful ways.

The following example shows how OpenNMS can be extended to detect missed executions for recurring activities like backups or scheduled jobs.