The 3.5 sec clock drift is not yet alarming but it does cause me to raise an
eyebrow. You are not synchronizing clocks between your Jenkins master, slave
and SCM server?
Try to get the clocks in sync. Install ntp daemon where it is missing and
configure them to sync to your organization's ntp s
I rebooted the machine and reran every job destined to be run on that Mac slave
node.
The all completed quickly and successfully.
Now, as I monitor the slave node, here's what I see for it:
Clock Difference:
3.5 sec ahead
Response Time
3410 ms
When I login to the machine (as myself, not the Jen
Here is more information, I just saw this message on the Manage Jenkins screen
(from the master node, about the mac slave with problems):
There are more SCM polling activities scheduled than handled, so the threads
are not keeping up with the demands. Check if your polling is hanging, and/or
in
Yes, I believe the Mac hardware is in good general health.
The machine has 3GB of physical memory, so I believe it has plenty of free
memory.
I don't believe it is swapping - but I'm not sure how to tell.
I have tried running Activity Monitor and JConsole.
As far as I can tell, there is no other s
Just to rule out the obvious culprits:
- The Mac hardware is in good general health?
- There is plenty of free memory? The system is not swapping?
- There isn't some process running and taking a lot of cpu? Spotlight indexing,
Time Machine backup, some anti-virus real-time scanner?
Even though
We are running Jenkins 1.478.
The master node is running on Windows 2003 (xp).
It has 3 slaves - 2 other Windos machines and 1 Mac.
The mac machine was working fine - then when I attempted to upgrade the O/S
(from Snow Leopard to Lion) it failed due to disk errors.
I've since reconstituted the mac
