forum.excito.com

Okay,

I just verified the client side scripting and if you enable easyfind through the web admin it will first run a php routine to check whether the chosen name is still available. Actually setting the name is run using a fairly complex route via backend.pl that acts as a front end to the Bubba.pm module which in turn uses 'system' call to run the easyfind.pl script in a separate perl instance. There is no error checking in this case because this type of call only allows checking the program return errorlevel and easyfind.pl does not set this - it only prints messages to stderr.

BTW: Who is?
- jotkwadrat @ 89.76.104.237 (Poland)
- backstrom @ 37.123.160.90 (Sweden)

BTW: Who is?
- jotkwadrat @ 89.76.104.237 (Poland)
- backstrom @ 37.123.160.90 (Sweden)

why? is this related to easyfind?

These are the current name holders I get back for two of the B3's that I own. Which is seriously strange since the secrets for both these B3's were never shared.

I'll have alook
Can they be mainboards for machines that were sent back within the trial period?

I don't think so, because these two both showed the previous error caused by record not being a record but containing the boolean value false. Somehow these were taken over, or I'm getting an incorrect result from the server and these actually belong to a different row in the database.

Edit: just wrote a new name to 'backstrom' and deleted it again. The first instance shows the same record id (2295) for my B3 and 'backstrom' does not list any more on ns1. The second instance gives me the not a hash error again.

Dont mess with the other one please, id like to have a look at the records tomorrow

Don't intend to. FYI id according to getname is 2296

I can give you access to the db backend if you like

Jotkwadrat is happily updating at this moment, but its not 2296 but 2301

2401
2015-02-24 18:39:05
2301
00:22:02:00:##:2a
p####vuJWz8xE+VisJ7V8REl58A=

2396
2015-02-19 15:52:19
2296
00:22:02:00:##:68
3jkv####3z8+LqCParTJ2s4cZ3Y=

I'm now getting the 'not a hash' error again. Don't know what happened or why it happened, but I sure did not invent this. Somehow I got fed information that did not belong to my B3.

Hi
I have six B3, that I bought before the bankruptcy.

Four are connected to internet.

Two oldest B3 have working esayfind. One of the two now working started to work OK since some days ago.

I will try to switch off and on easyfind on at B3 web to see if easyfind will start to function for two of the newest failed B3.

I have tried to follow this thread and I do not understand what a "B3 Id" is and where and how i can find it ?

I get the same error as in this thread for two of the newest.
/usr/lib/web-admin/easyfind.pl
Updating IP on file.
Wrote config to file
{"debug_uid":"ID765796648","msg":"function get_record_id failed for combination 00:22:02:00:##:76 and qW4dT#####moexiNu3HfEW9X50= (EF_ERR_501)","opcode":18,"record":{},"error":true,"operation":"Get record"}

I will put all six B3 on internet , later on, to see wich is working with easyfind.

It would be nice get all six functioning with the easyfind.


Best Reghards Bjorn Berglund

Trying easyfind .pl via command line without setting the configs correct is difficult, and its not worth spending time on. The web interface gives you an error report if there is a problem. Please post that error report

Thanks,

I have set easyfind "name" with webinterface without any problem in the past, when i recevived the B3 from excito.

I will try again, to set easyfind with webinterface to a new name and se if I get any error , and then back again to the name I was setting without problem in the past.

I will post any problem found here.

Best Regards Bjorn

Thanks again,

Now I have successfully updated the easyfind, to the old name I did initially used and it seems to work fine.
I will do the same later on with my remaning two B3 I have on another location.

Best Regards Banan

ok, good to hear the update has been successful.