-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Junaid,
Something's weird with the first reservation for the node that was assigned twice. This line from the log |4317|16698:16698|new| 2014-02-18 22:48:40|4317|16698:16698|new| utils.pm:check_time(1109)|reservation start time was in the past 17 minutes (-49) shows that it was not picked up for processing until it was 49 minutes after the start time for the reservation. Do you have your web server and database server on different systems? If so, are their times in sync? Josh On Wednesday, February 19, 2014 12:08:07 PM Junaid Ali wrote: > Hello, > > I had a failed reservation last night and the problem is related to an > already assigned VM being assigned to a new reservation. The VM " > vcl-vm-17" that was originally assigned to reservation # 16698 and then a > new reservation (# 16699) came in that tried to use the same VM and failed. > It looks like reservation # 16698 was not acknowledged by the user and > eventually timed-out, but this was after the reservation # 16699 had failed. > > Any ideas why VCL is trying to assign a busy VM to another reservation? > > The version of VCL is 2.2.1 > > VCLD log is available at: http://pastebin.com/WH1Srwuj > > > > Thanks. > > Junaid Ali - -- - ------------------------------- Josh Thompson VCL Developer North Carolina State University my GPG/PGP key can be found at pgp.mit.edu All electronic mail messages in connection with State business which are sent to or received by this account are subject to the NC Public Records Law and may be disclosed to third parties. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlMFGmMACgkQV/LQcNdtPQMNtQCeOYNkDPsdyK9xRsVNWSPCpZF2 s9QAn2WGjULOkBbRM/cLiHS+zquyV9fD =HSIu -----END PGP SIGNATURE-----
