-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Communication seems to work but no upload #23
Comments
That's it? There's no more log after that? |
Hi David, great you are still there, yes that's it. I can wait for ages but there is nothing more coming. I thing it hangs somewhere - as I even can not stop the server properly are there any special settings I should do when I configure the wifi Thanks for all your Help. Peter On 30/11/15 20:12, David Grant wrote:
|
I am seeing a similar issue. My logs are longer: [12/08/15 11:07PM][get_request] - Incoming connection from client 192.168.0.2 Traceback (most recent call last): |
Can you please post your .conf file? |
Hi David, I assume you mean the defaultsettings.ini which is this : Main configuration[Global] The directives in this section affect the overall operationof the Eye-Fi serverListenPort: Allows you to bind the Eye-Fi server to a specific port.#ListenPort=59278 ConsoleOutput: Logging can automatically be sent to the console.Set this to False if you don't want any console output. Consoleoutput is also considered stdout.ConsoleOutput=True LogFile: Controls where to write the Eye-Fi logs.#LogFile= LogLevel: The level of verbosity in both the logs and the consoleoutput. From most verbose to lease verbose the settings areDEBUG, INFO, WARNING, ERROR or CRITICALLogLevel=DEBUG DownloadLocation: The directory in which to put the incoming pictures. Bydefault the pictures are put in a sub directory called "pictures" fromwhere the script is originally started.#On Windows: This would set the downloads to a directory called pictures.#DownloadLocation=.\pictures #On Unix: ExecuteOnUpload: This parameter is used to define an external programor script to execute after a file is uploaded. By nature this command is verydangerous and should be used carefully. Enabling this command can serve as a means ofcompromising a system or disclosing information via bugs in external programs or scripts.This parameter executes the specified command on each incoming filepassing in the full file path as the first argument. There is no default for this command(nothing is executed if this parameter is left blank).#On Windows: #ExecuteOnUpload=C:\Windows\system32\mspaint.exe [Card] The directives in this section affect the physical card settingsUploadKey: The Eye-Fi upload key. It is in C:\Documents and Settings\\Application Data\Eye-Fi\Settings.xml. This needs to be set forthe server to function correctly.UploadKey=c686e547e3728c63a8f78729c1592757 regards Thanks for all your help Peter On 09/12/15 04:31, David Grant wrote:
|
Here is my eyefiserver.conf file from my QNAP TS-251 server. This worked fine on my TS-221 running QTS 4.2, but I've not gotten it to transfer files on my TS-251 (which is probably running a different build of 4.2). I don't have access to the old TS-221 anymore so I can't compare with it. I put single quotes in front of the comments below as github kept interpreting the hashes as formatting characters. The real file does not have the comments starting with a single quote. The version of Optware I am using is 0.99.163 from I couldn't find a version on github. eyefiserver.conf:
|
mjb9, on line 879, where it says: upload_key = mac_to_uploadkey_map[mac], right before that can you add a line that says "print "mac_to_uploadkey_map: ", mac_to_uploadkey_map" so it looks like:
|
Here are the logs. Seems to not like the "print "mac_to_uploadkey_map: ", mac_to_uploadkey_map" line now. BTW, the GUI sometimes stops working (even with "WebUI = QTS_desktop" in the qpkg.conf file.) The GUI behavior is intermittent, but I only used it to look at the logs. But I noticed that the log is stored in /var/log/eyefiserver.log [12/09/15 11:03PM][get_request] - Incoming connection from client 192.168.0.2 Traceback (most recent call last): Traceback (most recent call last): |
For some reason, and I don't have a clue as I changed nothing and the QNAP has not been restarted, it seems to be uploading. The GUI does not work, but I can live with that. I've also done some experiments running Eye-Fi's server inside a Win 7 VM instance using QNAP's Virtualization Station on a TS-251 with 8GB of RAM. It works as well as the Eye-Fi's server running directly on a PC, although it's a bit inefficient with the QNAP's resources. |
Hi, I've the same Issue... Is there any further process here? I'm trying to modify my raspberry to catch the pictures from the mobi pro. I added the
above the
in the py file. The logs are: [01/09/18 08:02PM][get_request] - Incoming connection from client 192.168.178.44 Traceback (most recent call last): Any ideas how to solve / proceed here? If there is any further information required, please let me know. Many thanks in advance. :-) |
Hi,
I'm a newbie in Linux and with this anyway. My Eyefi card ain my camera seems to communicate but it doesn't seem to upload any picture, not in the default directory nor any other.
This is the screenshot from the Server - what am I doing wrong ?
s1:StartSession>/SOAP-ENV:Body/SOAP-ENV:Envelope
[11/26/15 09:21AM][do_POST] - Got StartSession request
[11/26/15 09:21AM][startSession] - Delegating the XML parsing of startSession postData to EyeFiContentHandler()
[11/26/15 09:21AM][startSession] - Extracted elements: {'transfermode': u'16418', 'macaddress': u'00185621140b', 'cnonce': u'c166667ce6dba80a7281b17bd75fe55e', 'transfermodetimestamp': u'1448406154'}
[11/26/15 09:21AM][startSession] - Setting Eye-Fi upload key to c686e547e3728c63a8f78729c1592757
[11/26/15 09:21AM][startSession] - Concatenated credential string (pre MD5): 00185621140bc166667ce6dba80a7281b17bd75fe55ec686e547e3728c63a8f78729c1592757
[11/26/15 09:21AM][do_POST] - StartSession response: <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">SOAP-ENV:Body5d1382e08a89c2a367b2d1095a1df8c93b7674c8e07db92df6c098d9fcd742b2164181448406154false/SOAP-ENV:Body/SOAP-ENV:Envelope
192.168.1.110 - - [26/Nov/2015 09:21:07] "POST /api/soap/eyefilm/v1 HTTP/1.1" 200 -
[11/26/15 09:21AM][get_request] - Incoming connection from client 192.168.1.110
[11/26/15 09:21AM][finish_request] - Creating instance of main.EyeFiRequestHandler to service request from ('192.168.1.110', 8578)
The text was updated successfully, but these errors were encountered: