Page 1 of 1

cannot login to webadmin or insigt/importer after XP install

PostPosted: Mon May 16, 2011 1:05 am
by epoxypatch
Hi,
I believe I followed your install instructions for windows to a T, and all things **seemed** to be giving the expected response during installment. However, I cannot seem to get past the webadmin web window (cannot connect, check your user and login) or the insight/importer window (login failed). I tried all variations of username and password, and even tried making everything 'omero', but no success. Here is the diagnostics screen :


================================================================================

OMERO Diagnostics Beta4.2.2-r8718-Beta4.2-b56
================================================================================


Commands: java -version 1.6.0 (C:\WINDOWS\system32\java.E
XE)
Commands: python -V 2.5.5 (C:\Python25\python.EXE)
Commands: icegridnode --version 3.3.1 (C:\Ice-3.3.1\bin\icegridno
de.EXE)
Commands: icegridadmin --version 3.3.1 (C:\Ice-3.3.1\bin\icegridad
min.EXE)
Commands: psql --version not found

Server: icegridnode running
Server: Blitz-0 active (pid = 4756, enabled)
Server: DropBox active (pid = 2228, enabled)
Server: FileServer active (pid = 4456, enabled)
Server: Indexer-0 active (pid = 2412, enabled)
Server: MonitorServer active (pid = 1156, enabled)
Server: OMERO.Glacier2 active (pid = 2748, enabled)
Server: OMERO.IceStorm active (pid = 1816, enabled)
Server: Processor-0 active (pid = 4552, enabled)
Server: Repository-1 error: node `repo' couldn't be reache
d:
the node is not active
Server: Tables-0 inactive (disabled)
Server: TestDropBox inactive (enabled)

Log dir: C:\omero_dist\var\log exists

Log files: Blitz-0.log 1.0 MB errors=4 warnings=12
0
Log files: DropBox.log 6.0 KB errors=0 warnings=2

Log files: FileServer.log 2.0 KB
Log files: Indexer-0.log 6.0 MB errors=2077 warnings=36
9
Log files: MonitorServer.log 4.0 KB
Log files: OMEROweb.log 33.0 KB errors=0 warnings=1

Log files: Processor-0.log 10.0 KB errors=1 warnings=9

Log files: Tables-0.log n/a
Log files: TestDropBox.log n/a
Log files: master.err 0.0 KB
Log files: master.out 0.0 KB
Log files: Total size 7.83 MB

Parsing Blitz-0.log:[line:77] => Server restarted <=
Parsing Blitz-0.log:[line:581] => Server restarted <=
Parsing Blitz-0.log:[line:699] => Server restarted <=
Parsing Blitz-0.log:[line:6345] => Server restarted <=
Parsing Blitz-0.log:[line:7537] => Server restarted <=

Environment:OMERO_HOME=(unset)
Environment:OMERO_NODE=(unset)
Environment:OMERO_MASTER=(unset)
Environment:PATH=C:\Python25\;C:\WINDOWS\system32;C:\WINDOWS;C:\WINDOWS\System32
\Wbem;C:\Program Files (x86)\ATI Technologies\ATI.ACE\Core-Static;C:\Program Fil
es (x86)\PerkinElmerCTG\bin;C:\Program Files\MATLAB\R2009a\bin;C:\Program Files\
MATLAB\R2009a\bin\win64;C:\Program Files (x86)\ATI\ATI.ACE\Core-Static;C:\Progra
m Files (x86)\QuickTime\QTSystem\;C:\Ice-3.3.1\bin
Environment:ICE_HOME=(unset)
Environment:LD_LIBRARY_PATH=(unset)
Environment:DYLD_LIBRARY_PATH=(unset)

OMERO data dir: '/OMERO' Exists? True Is writable? True
OMERO.web status... DEVELOPMENT: You will have to check status by hand!


Any help would be great! Thanks a lot
gagan

Re: cannot login to webadmin or insigt/importer after XP ins

PostPosted: Mon May 16, 2011 8:20 am
by jmoore
Hi Gagan,

did you also try using the username "root" and the password you provided to "bin\omero db script" ? When you first log in, your OMERO system doesn't have a user "omero". See "Which password do I use where?" from our "Troubleshooting" page for more information.

Cheers,
~Josh.

Re: cannot login to webadmin or insigt/importer after XP ins

PostPosted: Wed May 18, 2011 5:59 pm
by epoxypatch
Dear Josh,
Thanks for your reply. Yes I did try 'root' as user name and my password, which I set up as 'omero' in the omero db script file. It did not work - any ideas?
gagan

Re: cannot login to webadmin or insigt/importer after XP ins

PostPosted: Wed May 18, 2011 6:11 pm
by jmoore
Could you post your var\log\Blitz-0.log file? If you know "root" / "omero" to be a working combination, then hopefully the log will show us what could be going wrong.

Thanks,
~Josh

Re: cannot login to webadmin or insigt/importer after XP ins

PostPosted: Wed May 18, 2011 6:46 pm
by epoxypatch
Dear Josh,
Here it is. Thanks a lot!

Re: cannot login to webadmin or insigt/importer after XP ins

PostPosted: Wed May 18, 2011 7:55 pm
by epoxypatch
I don't know if this is useful but my DYLD library paths list is 'unset' in the diagnostics output. Is that normal? I have set the environment variable path for Ice as the instructions said, but that was to the ICE /bin subdirectory, not the /lib directory.

-------------------------------------------
Environment:ICE_HOME=(unset)
Environment:LD_LIBRARY_PATH=(unset)
Environment:DYLD_LIBRARY_PATH=(unset)

Also when trying to access webadmin I don't get a 'wrong user name or password', but nothing happens after I hit connect, the screen appears to take the input but it doesn't move beyond the login screen, it just refreshes the input fields.

Re: cannot login to webadmin or insigt/importer after XP ins

PostPosted: Fri May 20, 2011 3:19 am
by jmoore
epoxypatch wrote:I don't know if this is useful but my DYLD library paths list is 'unset' in the diagnostics output. Is that normal? I have set the environment variable path for Ice as the instructions said, but that was to the ICE /bin subdirectory, not the /lib directory.

-------------------------------------------
Environment:ICE_HOME=(unset)
Environment:LD_LIBRARY_PATH=(unset)
Environment:DYLD_LIBRARY_PATH=(unset)


DYLD_ and LD_LIBRARY_PATH are only of use on Unix systems.

Also when trying to access webadmin I don't get a 'wrong user name or password', but nothing happens after I hit connect, the screen appears to take the input but it doesn't move beyond the login screen, it just refreshes the input fields.


Now that we know the password you are using is correct (I also checked that you are successfully logging in via the log), could you try again as root with Insight. We've seen similar problems from other users on XP where the development web server fails to work properly. You might try deploying the production version. Alternatively, you can help us debug the XP/development server problem by sending us the OMERO.web log.

Cheers,
~Josh