This was resolved by deleting some offending entries from the 'request'
table. I found a thread in the vcl-user archive [1] regarding a similar
problem that suggested deleting entries from 'request' where the statid was
either 10 or 18.
I've pasted some of the offending entries below. Is there any
documentation on these state IDs? I found the database scheme on the cwiki
site[2][3] but can't find any info on the id number-to-state translation.
I ended up deleting all of the entries in 'request,' which cleaned up both
the errant vcld log entries (trying to change state to maintenance) and the
inability to click "Virtual Hosts -> Configure Host" for a particular VM
host. Interestingly, there were requests hung up for BOTH VM hosts, but
only one of the two would fail to load in the VCL admin UI.
Thoughts on why this happens (not so much the UI hanging, but the dangling
entries in 'request') and whether there could be either an automated
cleanup or something an admin could trigger via the UI without fishing in
the DB?
id | stateid | userid | laststateid | logid | forimaging | test | preload
| start | end | daterequested |
datemodified | checkuser |
+-----+---------+--------+-------------+-------+------------+------+---------+---------------------+---------------------+---------------------+--------------+-----------+
| 1 | 10 | 1 | 16 | 0 | 0 | 0 |
0 | 2014-02-19 09:00:45 | 2014-02-19 10:00:45 | 2014-02-19 09:00:45 | NULL
| 1 |
| 230 | 14 | 2 | 19 | 0 | 0 | 0 |
0 | 2014-04-25 17:00:00 | 2014-04-25 17:20:00 | 2014-04-25 17:08:27 | NULL
| 1 |
| 380 | 14 | 2 | 19 | 0 | 0 | 0 |
0 | 2014-04-29 14:30:00 | 2014-04-29 14:50:00 | 2014-04-29 14:31:34 | NULL
| 1 |
| 477 | 14 | 2 | 18 | 0 | 0 | 0 |
0 | 2014-04-29 19:15:00 | 2014-05-30 19:15:00 | 2014-04-29 19:23:56 | NULL
| 1 |
| 478 | 14 | 2 | 18 | 0 | 0 | 0 |
0 | 2014-04-29 19:15:00 | 2014-05-30 19:15:00 | 2014-04-29 19:23:56 | NULL
| 1 |
| 479 | 14 | 2 | 18 | 0 | 0 | 0 |
0 | 2014-04-29 19:15:00 | 2014-05-30 19:15:00 | 2014-04-29 19:23:56 | NULL
| 1 |
| 480 | 14 | 2 | 18 | 0 | 0 | 0 |
0 | 2014-04-29 19:15:00 | 2014-05-30 19:15:00 | 2014-04-29 19:23:56 | NULL
| 1 |
| 481 | 14 | 2 | 18 | 0 | 0 | 0 |
0 | 2014-04-29 19:15:00 | 2014-05-30 19:15:00 | 2014-04-29 19:23:56 | NULL
| 1 |
[1] http://markmail.org/message/qnk6y5e4einwmgrc
[2] https://cwiki.apache.org/confluence/display/VCL/Database+Schema
[3] https://cwiki.apache.org/confluence/display/VCL/States
mth
On Tue, Apr 29, 2014 at 6:41 PM, Lo Richard <[email protected]> wrote:
> Hi Josh
>
> Thanks for the suggestion. Unfortunately it did not change my situation. I
> still have problems loading my 2nd virtual host 'vcl02'. It just loads into
> perpetuity on the admin page, although vcl01 loads fine.
>
> Also to note trying to move baseimage to unassigned VM I had a strange
> screen (baseimage.jpg). The servers dates and times are all correct.
>
> So right now VM's assigned to vcl02 still work and are able to load images
> but I cant unassign or rearrange VM assignments for vcl02.
> My vcld.log just shows the following:
>
>
>
> 2014-04-29 15:38:16|29556|vcld:main(167)|lastcheckin time updated for
> management node 1: 2014-04-29 15:38:16
> 2014-04-29
> 15:38:16|29556|189:189|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 69142 minutes
> 2014-04-29
> 15:38:16|29556|428:428|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 99382 minutes
> 2014-04-29
> 15:38:16|29556|443:443|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 109462 minutes
> 2014-04-29
> 15:38:16|29556|193:193|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 79222 minutes
> 2014-04-29
> 15:38:16|29556|42:42|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 38902 minutes
> 2014-04-29
> 15:38:16|29556|154:154|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 48982 minutes
> 2014-04-29
> 15:38:16|29556|444:444|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 99382 minutes
> 2014-04-29
> 15:38:16|29556|292:292|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 89302 minutes
> 2014-04-29
> 15:38:16|29556|44:44|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 38902 minutes
> 2014-04-29
> 15:38:16|29556|159:159|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 59062 minutes
> 2014-04-29
> 15:38:16|29556|161:161|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 59062 minutes
> 2014-04-29
> 15:38:16|29556|156:156|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 48982 minutes
> 2014-04-29
> 15:38:16|29556|429:429|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 89302 minutes
> 2014-04-29
> 15:38:16|29556|293:293|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 79222 minutes
> 2014-04-29
> 15:38:16|29556|195:195|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 69142 minutes
> 2014-04-29 15:38:21|29556|vcld:main(167)|lastcheckin time updated for
> management node 1: 2014-04-29 15:38:21
> 2014-04-29
> 15:38:21|29556|189:189|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 69142 minutes
> 2014-04-29
> 15:38:21|29556|428:428|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 99382 minutes
> 2014-04-29
> 15:38:21|29556|443:443|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 109462 minutes
> 2014-04-29
> 15:38:21|29556|193:193|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 79222 minutes
> 2014-04-29
> 15:38:21|29556|42:42|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 38902 minutes
> 2014-04-29
> 15:38:21|29556|154:154|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 48982 minutes
> 2014-04-29
> 15:38:21|29556|444:444|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 99382 minutes
> 2014-04-29
> 15:38:21|29556|292:292|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 89302 minutes
> 2014-04-29
> 15:38:21|29556|44:44|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 38902 minutes
> 2014-04-29
> 15:38:21|29556|159:159|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 59062 minutes
> 2014-04-29
> 15:38:21|29556|161:161|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 59062 minutes
> 2014-04-29
> 15:38:21|29556|156:156|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 48982 minutes
> 2014-04-29
> 15:38:21|29556|429:429|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 89302 minutes
> 2014-04-29
> 15:38:21|29556|293:293|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 79222 minutes
> 2014-04-29
> 15:38:21|29556|195:195|tomaintenance|utils.pm:check_time(1127)|tomaintenance
> request will be processed in 69142 minutes
>
> Thanks
>
> --
> Richard Lo
> Systems Manager
> Whittier College
> [email protected]
>
> -----Original Message-----
> From: Josh Thompson [mailto:[email protected]]
> Sent: Tuesday, April 29, 2014 1:49 PM
> To: [email protected]
> Subject: Re: stuck at selecting virtual host
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Richard,
>
> This might be due to an incompatibility between the Dojo Toolkit version
> in the last VCL release and updates that have been done in web browsers
> since then. There is a newer version of the Dojo Toolkit available to
> address these changes. You can download a version I customized to work
> with VCL here:
>
> http://people.apache.org/~jfthomps/updates/dojo-1.6.2.tar.bz2
>
> Extract that in your root vcl web directory. Then, rename the existing
> "dojo"
> directory to something like "dojo.old" and rename the newly extracted
> "dojo-1.6.2" directory to "dojo". Finally, reload the Virtual Hosts part
> of the web site to see if that fixed your problem.
>
> Josh
>
> On Monday, April 28, 2014 8:16:43 PM Lo Richard wrote:
> > Last Friday I ran a yum update to my web front end, repository, and
> > two management servers all running Centos 5.1. In this order.
> >
> > 1. Web Front End
> > 2. Repository
> > 3. Management1 (residing on Vcl1)
> > 4. Management2 (residing on Vcl02)
> >
> > Each server was rebooted and up before the subsequent server is
> > rebooted so they werent all rebooted at once. After the reboot and
> > reallocated VM's back to respective virtual hosts I noticed some VM's
> were failing to load.
> > Upon further examination I noticed that it was because about 4 of them
> > never made it to the management2 host. I proceeded to re add them to
> > Virtual Host and select VCL02 and noticed that it just sits as the
> > progress ball spins. VCL01 comes up right away but nothing for VCL02
> > under virtual host. Did a reboot on managment2 to see if things would
> > come back up, nothing changed.
> >
> > I did a tail -f on vcld.log on management 2 and see constant outputting:
> >
> > 2014-04-28 13:10:45|4022|vcld:main(167)|lastcheckin time updated for
> > management node 2: 2014-04-28 13:10:45 2014-04-28
> > 13:10:45|4022|155:155|tomaintenance|utils.pm:check_time(1127)|tomainte
> > nance request will be processed in 50569 minutes 2014-04-28
> > 13:10:45|4022|295:295|tomaintenance|utils.pm:check_time(1127)|tomainte
> > nance request will be processed in 90889 minutes 2014-04-28
> > 13:10:45|4022|188:188|tomaintenance|utils.pm:check_time(1127)|tomainte
> > nance request will be processed in 80809 minutes 2014-04-28
> > 13:10:45|4022|158:158|tomaintenance|utils.pm:check_time(1127)|tomainte
> > nance request will be processed in 70729 minutes 2014-04-28
> > 13:10:45|4022|294:294|tomaintenance|utils.pm:check_time(1127)|tomainte
> > nance request will be processed in 80809 minutes 2014-04-28
> > 13:10:45|4022|46:46|tomaintenance|utils.pm:check_time(1127)|tomaintena
> > nce request will be processed in 50569 minutes 2014-04-28
> > 13:10:45|4022|162:162|tomaintenance|utils.pm:check_time(1127)|tomainte
> > nance request will be processed in 60649 minutes 2014-04-28
> > 13:10:45|4022|157:157|tomaintenance|utils.pm:check_time(1127)|tomainte
> > nance request will be processed in 50569 minutes 2014-04-28
> > 13:10:45|4022|197:197|tomaintenance|utils.pm:check_time(1127)|tomainte
> > nance request will be processed in 80809 minutes 2014-04-28
> > 13:10:45|4022|190:190|tomaintenance|utils.pm:check_time(1127)|tomainte
> > nance request will be processed in 90889 minutes 2014-04-28
> > 13:10:45|4022|194:194|tomaintenance|utils.pm:check_time(1127)|tomainte
> > nance request will be processed in 70729 minutes 2014-04-28
> > 13:10:45|4022|291:291|tomaintenance|utils.pm:check_time(1127)|tomainte
> > nance request will be processed in 100969 minutes 2014-04-28
> > 13:10:45|4022|160:160|tomaintenance|utils.pm:check_time(1127)|tomainte
> > nance request will be processed in 60649 minutes 2014-04-28
> > 13:10:45|4022|41:41|tomaintenance|utils.pm:check_time(1127)|tomaintena
> > nce request will be processed in 40489 minutes 2014-04-28
> > 13:10:45|4022|153:153|tomaintenance|utils.pm:check_time(1127)|tomainte
> > nance request will be processed in 60649 minutes 2014-04-28
> > 13:10:45|4022|45:45|tomaintenance|utils.pm:check_time(1127)|tomaintena
> > nce request will be processed in 40489 minutes 2014-04-28
> > 13:10:45|4022|43:43|tomaintenance|utils.pm:check_time(1127)|tomaintena
> > nce request will be processed in 40489 minutes 2014-04-28
> > 13:10:45|4022|196:196|tomaintenance|utils.pm:check_time(1127)|tomainte
> > nance request will be processed in 70729 minutes
> >
> > Also when using the console to monitor the page, selecting anything
> > other than the default vm host from the pull down menu and clicking
> > the button yields a dojo.js error:
> >
> > missing ) in parenthetical
> >
> > line 14
> >
> > Actually loading images and running reservations from Management2 work
> > fine I am just not able to allocate or unallocate VM's in Virtual Host
> > from the admin page.
> >
> > Any help would be appreciated.
> >
> > -
> > Richard Lo
> > IT Services
> > Whittier College
> > [email protected]<mailto:[email protected]>
> - --
> - -------------------------------
> 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)
>
> iEYEARECAAYFAlNgECoACgkQV/LQcNdtPQOqXQCfZ3ATPkoqv88xY+Gz+zpRvjg4
> rCsAn3Bu0QRpXkPAfeFQaUUa88xjVcV+
> =Gd6T
> -----END PGP SIGNATURE-----
>
>
