Author
Topic: Trouble logging in (Read 19225 times)

I (think I) successfully installed from the Debian quickstart package. However, when I go to log in to the web-based admin page, it says that my password is not correct. It also says that the initial user name and password should be the same as this site, which I checked again: They are. There was one additional issue with naming of the machine: dce_router is not a possible name, as underscores returned an error, and a message that they are not legal in naming of machines. So, I named it dce-router. Any help with the admin login problem would be gratefully appreciated.

That is odd. Are you familiar with a Linux console, and how to login? If so, please login as root and type this:mysql#That will start the sql database client and give you a mysql> prompt, at which type:use pluto_mainselect * FROM Users;#You should then see the contents of your Users table, and there should be 1 record with your user info. If you don't see any records, please do a "select * FROM Device;" and let me know if you have records in the Device table. The 'password' column contains your password as an md5 hash. If you want to see a password as md5, type this:select md5('foo');# where 'foo' is what you think your password is. That will show you your password as an md5 hash. Is it the same as the md5 column? If not, then somehow the password is different. Please e-mail me the md5 hash that is in your table to aaron.b at plutohome dot com, and I'll check to see if it's the same as on our server. If you want to change the password, type this:update Users set Password=md5('newpassword');#to set the password to [newpassword]. Type 'quit' at the mysql> prompt to exit mysql and return to the Linux console. Whenever you login with the pluto-admin site your password is validated against that Users table in your local database. So the failure was either (a) that the user record wasn't pulled from the plutohome.com website, or (b) that the password in your local database is not what you think, or (c) that there's a problem with the pluto-admin page. Please let me know so we can figure out what went wrong and be sure to correct it. Thanks.

Aaron,It appears that there are no records in the Users or Device tables, which would explain why I couldn't log in. Why the installer did not create the records is a different question. I will attempt to create the record for user, but for device there could be an issue...

The database is populated with it's initial data during the DCERouter's post install script. This gets run automatically when you install the Debian packages. Did you install with Debian, or by source, or a .tar file?

All our internal testing is with Debian and using the Debian packages. There are actually quite a few post install scripts that need to be run for everything to work. The programmer who is responsible for all the scripts is a bit behind schedule and has not yet started created rpm packages and other mechanisms for doing the same thing on a non-debian system.

If your system is non-debian, just try running the wget and the mysql command manually.

Aaron,Thanks for your help.I *did* do the install from the Debian Quickstart CD downloaded from PH, which is why I was a little surprised that it hadn't successfully run the mySQL scripts. It wasn't a network issue, as most of the packages appear to have installed correctly, and they were downloaded.I will either run the scripts that you suggest from the command line, or perhaps try running the Quickstart again over the top of my current installation. Any other suggestions?Best,Nik

I had a look at initialdata.php on my browser, and it looks like a SQL script file should look, (very well commented, by the way!), and contains the correct data for myself and my devices. The issue clearly seems to be that the field FK_Device_Audio doesn't exist, and therefore an error is thrown.

I am no a real wiz at mySQL nor Linux, and so I will refrain for the moment from bumping around looking for the original SQL script used to create the table, but it seems that may be where the problem is.Best,Nik

that explains everything. Thanks. It's an error in the database synchronization between our production server and our in-house development one. We will post a new release (hopefully) tomorrow or the next day that will fix this. You will probably just want to redo the kick-start cd then. You will see on our website in the 'news' section the moment the updated version is posted.

Can you tell me what is your installation number so I can do some checking? You can see what the installation number is both in the "My Pluto" section on the website and in /etc/pluto.conf on your system as "FK_Installation=<number>"

There was a field FK_Device_Audio in the table Device, database pluto_main. But it was removed over a month ago. I checked and our main server's schema is properly synced (ie the field isn't there). And in the current kick-start cd also the field isn't there. So I don't know where it's coming from. Is this an old kick-start cd? Do you know what version it is? The initial boot screen says the version in the lower-left corner. It's harmless to boot the cd to that point--it doesn't do anything there but show the welcome screen.

Never mind. I just noticed that the thread with the reference to FK_Device_Audio was made in December -- this is a new post to an old thread. So I think that the cause of your problem is somehow different and not related to FK_Device_Audio.

It is a Kick Start image I downloaded from install 1348 yesterday as I needed to reinstall the core. I created the 6422, after I had the logon issue with install 1348 but did not download the kickstart image again, I didn't realise that the kickstart CD's where install specific...

The initial data looks fine here. Did you get any errors while doing the install? Also, tell me if your /usr/pluto/install/database_initial_data.sql file contains data (lines starting with INSERT), especially a line starting with "INSERT INTO `Users`