Skip to content
Paul Houle edited this page Jun 3, 2014 · 3 revisions

This is a list of boundary cases and confusing things you might experience working with RDFeasy.

System takes 10-20 minutes to initialize on first boot

If you log into your instance shortly after launching it, you will see the message.

Database is still initializing.  When initialization is complete
database credentials will appear on login

This is not unusual because it can take a few minutes (often 10 or so) for Virtuoso to boot up for the first time with a large database. In this period of time you cannot log into the database with either the sql command or the web interface at port 8890. All you can do is wait until Virtuoso comes up, after which a new password is assigned and the database becomes available.

The best remedy is to take a break for ten minutes, log in again via ssh, and you will hopefully see something like:

Log into the virtuoso database with the following credentials:

username: dba
password: 0jzSyNOhvfchQfLL

Note this password is randomly generated, so it is safe for me to cut and paste this into the wiki because I just terminated the machine in question. (This is the whole point, because generating a random password on boot is a requirement of the AWS marketplace.)

You shouldn't make any changes to the machine (including OS updates) until the system has booted for the first time and the password is assigned.

NOTE

When Virtuoso is initializing, you will see a Virtuoso database running.

ubuntu@ip-10-95-165-234:~$ ps auwx | grep virtuoso
ubuntu    1857  0.0 42.8 24342176 13354152 ?   Ssl  May21  10:04 ../../../../bin/virtuoso-t +configfile /usr/local/virtuoso-opensource/var/lib/virtuoso/db/virtuoso.ini
ubuntu    9411  0.0  0.0   8172   948 pts/1    S+   19:28   0:00 grep --color=auto virtuoso
ubuntu@ip-10-95-165-234:~$

If you find the system still has no password after long time and you cannot find the virtuoso-t process, you have found a bug.

Note that after the first boot, the system will retain the password generated at first boot so this problem will not recur. Second and subsequent boots are faster than first boots.