Thanks for that... it looks as if my problem goes a tad deeper though (wouldn't ya just know it!!).
When I run that, I get a bunch of messages :-
005 Corrupt next header at 0xC84 in KDBF file d:\apps\thunde~1\webinator\texis\testdb\SYSTRIG.tbl: Probable 64-bit file; convert to 32-bit via addtable in the function read_rest_data
005 Corrupt next header at 0xC84 in KDBF file
d:\apps\thunde~1\webinator\texis\testdb\SYSTRIG.tbl: Probable 64-bit file; convert to 32-bit via addtable in the function read_rest_data
005 Corrupt next header at 0x29FA in KDBF file d:\apps\thunde~1\webinator\texis\testdb\SYSTABLE.tbl: Probable 64-bit file; convert to 32-bit via addtable in the function read_rest_data
005 Corrupt block header at 0x29FA in KDBF file
d:\apps\thunde~1\webinator\texis\testdb\SYSTABLE.tbl: Probable 64-bit file; convert to 32-bit via addtable in the function read_head
005 Corrupt next header at 0x1246 in KDBF file d:\apps\thunde~1\webinator\texis\testdb\SYSPERMS.tbl: Probable 64-bit file; convert to 32-bit via addtable in the function read_rest_data
005 Corrupt block header at 0x1246 in KDBF file
d:\apps\thunde~1\webinator\texis\testdb\SYSPERMS.tbl: Probable 64-bit file; convert to 32-bit via addtable in the function read_head
005 Corrupt block header at 0xC84 in KDBF file d:\apps\thunde~1\webinator\texis\testdb\SYSTRIG.tbl: Probable 64-bit file; convert to 32-bit via addtable in the function read_head
005 Corrupt next header at 0x15F4 in KDBF file d:\apps\thunde~1\webinator\texis\testdb\SYSINDEX.tbl: Probable 64-bit file; convert to 32-bit via addtable in the function read_rest_data
005 Corrupt block header at 0x15F4 in KDBF file d:\apps\thunde~1\webinator\texis\testdb\SYSINDEX.tbl: Probable 64-bit file; convert to 32-bit via addtable in the function read_head
005 Corrupt next header at 0xD64 in KDBF file d:\apps\thunde~1\webinator\texis\testdb\SYSUSERS.tbl: Probable 64-bit file; convert to 32-bit via addtable in the function read_rest_data
006 Can't write to KDBF file d:\apps\thunde~1\webinator\texis\testdb\SYSUSERS.tbl: Corruption detected in the function kdbf_put
005 Corrupt next header at 0xD64 in KDBF file d:\apps\thunde~1\webinator\texis\testdb\SYSUSERS.tbl: Probable 64-bit file; convert to 32-bit via addtable in the function read_rest_data
000 Could not write updated record in the function update
Looks like the lack of a login is down to corruption... do I have anywhere to go, or is it re-install time?
Pretty much the opposite actually. But the suggestion gave me a clue and I have sorted the problem. Turns out the commercial version wasn't installed over the free version, and I think I was simply hitting the wrong database set.
Resolved.
Thanks for the assistance... VERY much appreciated.
and the system does seem to prompt for a new password. However, it seems
to reject all such passwords. The login screen says
Search Appliance Administration Set Password
-- First time setup. --
Your administrative password needs to be set to prevent unauthorized access
to your databases.
Initial password already configured.
Please choose a password that is easy for you to remember but hard for someone
else to guess. You need to enter the same password in both boxes to protect
against typing mistakes. Passwords are case sensitive.
Password for user admin:
That "Initial password already configured." bothers me; is it a clue to the
problem?
- Cameron Simpson
Those instructions apply to webinator, not the appliance. The appliance is not supposed to be hacked. You'll either have to reinstall to factory state using the CD that came with the appliance and lose all crawl data. Or make sure the appliance is accessable via the internet on port 22 and open a tech support ticket so that support personnel may connect to it and clean it up without losing crawl data.
Ok, I guess I have to go the support route. The appliance is a replacement for our previous thunderstone that died. As far as I know it didn't come with a piece of paper with the default password (but I didn't unpack it). It's already in the "blank install from CDROM" state (which is fine, because we want to completely redo what it crawls anyway).
Thanks for the reply though. I'll get on the telephone then. There is practially no likelyhood that we'll expose this box to the internet though.
If it's in factory state it will have the password that your original appliance had. It's printed on the inside cover of the installation/getting started manual. Or tech support can provide it to a known contact via email or phone.
Well I thought that too. But the reason I was even trying to hack it is that the password in the inside cover of the Getting Started Guide (from the original box) didn't work:-(
Well, I've submitted twice to the "Tech Support Request" form (we do have a maintenance contract) and heard nothing. Can somebody please contact us directly? If not me (Cameron Simpson cameron@research.canon.com.au) then Daniel Smith daniels@research.canon.com.au.