SOLVED Webdav not working in 2014-10-25 nightly

[Smitterson]

Not sure if I need to do something special, but when I try to enable the Webdav service, I get a "This service could not be started" error. I just updated to 9.3-M4 today.

Has anyone else been able to get this working? Or does anyone know which log may contain more details on why webdav is failing to start??

 

[Ismael Duarte]

Same here

Oct 25 18:44:57 duarte notifier: no listening sockets available, shutting down
Oct 25 18:44:57 duarte notifier: AH00015: Unable to open logs
Oct 25 18:44:57 duarte root: /usr/local/etc/rc.d/apache24: WARNING: failed to start apache24
Oct 25 18:44:57 duarte notifier: /usr/local/etc/rc.d/apache24: WARNING: failed to start apache24
Oct 25 18:45:01 duarte syslog-ng[27855]: Error binding socket; addr='AF_INET(0.0.0.0:514)', error='Address already in use (48)'
Oct 25 18:45:01 duarte syslog-ng[27855]: Initiating connection failed, reconnecting; time_reopen='60'
Oct 25 18:45:49 duarte notifier: Will not 'reload' apache24 because apache24_enable is NO.
Oct 25 18:46:01 duarte syslog-ng[27855]: Error binding socket; addr='AF_INET(0.0.0.0:514)', error='Address already in use (48)'
Oct 25 18:46:01 duarte syslog-ng[27855]: Initiating connection failed, reconnecting; time_reopen='60'
Oct 25 18:47:01 duarte syslog-ng[27855]: Error binding socket; addr='AF_INET(0.0.0.0:514)', error='Address already in use (48)'
Oct 25 18:47:01 duarte syslog-ng[27855]: Initiating connection failed, reconnecting; time_reopen='60'
Oct 25 18:48:01 duarte syslog-ng[27855]: Error binding socket; addr='AF_INET(0.0.0.0:514)', error='Address already in use (48)'
Oct 25 18:48:01 duarte syslog-ng[27855]: Initiating connection failed, reconnecting; time_reopen='60'
Oct 25 18:49:01 duarte syslog-ng[27855]: Error binding socket; addr='AF_INET(0.0.0.0:514)', error='Address already in use (48)'
Oct 25 18:49:01 duarte syslog-ng[27855]: Initiating connection failed, reconnecting; time_reopen='60'
Oct 25 18:50:01 duarte syslog-ng[27855]: Error binding socket; addr='AF_INET(0.0.0.0:514)', error='Address already in use (48)'
Oct 25 18:50:01 duarte syslog-ng[27855]: Initiating connection failed, reconnecting; time_reopen='60'
Oct 25 18:51:01 duarte syslog-ng[27855]: Error binding socket; addr='AF_INET(0.0.0.0:514)', error='Address already in use (48)'
Oct 25 18:51:01 duarte syslog-ng[27855]: Initiating connection failed, reconnecting; time_reopen='60'
Oct 25 18:52:01 duarte syslog-ng[27855]: Error binding socket; addr='AF_INET(0.0.0.0:514)', error='Address already in use (48)'
Oct 25 18:52:01 duarte syslog-ng[27855]: Initiating connection failed, reconnecting; time_reopen='60'
Oct 25 18:53:01 duarte syslog-ng[27855]: Error binding socket; addr='AF_INET(0.0.0.0:514)', error='Address already

 

[Smitterson]

Ok, glad it's just not me. What log contained those messages? Or do you just want to open a bug report so the devs know about the issue?

 

[cyberjock]

Please check the open tickets and see if WebDAV has actually done being developed. It could be something they are actively developing and isn't expected to work right now. ;)

 

[Smitterson]

Please check the open tickets and see if WebDAV has actually done being developed. It could be something they are actively developing and isn't expected to work right now. ;)

I didn't see any open tickets related to WebDAV in any of the 9.3 related lists on bugs.freenas.org, so I assumed it was meant to work. Totally fine if it's not, I know 9.3 isn't even beta yet.

 

[cyberjock]

I didn't see any open tickets related to WebDAV in any of the 9.3 related lists on bugs.freenas.org, so I assumed it was meant to work. Totally fine if it's not, I know 9.3 isn't even beta yet.

That's a very good assumption to make. I don't know much of anything about WebDAV so I can't really tell you how it "should" work. :P

Just trying to kind of get people to "feel out" what this section of the forum is and isn't for since I just created it.

 

[mjws00]

I got it working on an earlier release. Haven't updated for a week or two. Never tried anything beyond "this is interesting, I can browse, write a file etc." I don't use it day to day either, so no pro here.

 

[Suraj Ravichandran]

Sorry it indeed was broken......I have fixed it (before i saw this message)

I did some major code revisions to it and some of my changes were half-hazard so it broke things.

I am running some tests on it myself, before I can claim completely and beyond an iota of doubt fixed status.

However, as a result of the said code changes WebDAV now uses the new cert UI to let it have a dedicated cert, and I also bumped the openssl on apache to use the ports version of openssl (so now we are more secure)

 

[Smitterson]

Sorry it indeed was broken......I have fixed it (before i saw this message)

I did some major code revisions to it and some of my changes were half-hazard so it broke things.

I am running some tests on it myself, before I can claim completely and beyond an iota of doubt fixed status.

However, as a result of the said code changes WebDAV now uses the new cert UI to let it have a dedicated cert, and I also bumped the openssl on apache to use the ports version of openssl (so now we are more secure)

No worries! I was expecting things to be broken in 9.3. I was just interested in trying it out to see first hand what you guys have been working on and see if I could help by finding bugs, etc. Looking forward to the release of 9.3 :)

 

[Ismael Duarte]

Just updated now, still not working for me. Now I can enable webdav but can't disable it. ;)
The log looks more less the same

Code:

Oct 26 13:57:20 duarte notifier: apache24 not running? (check /var/run/httpd.pid).
Oct 26 13:57:20 duarte notifier: Will not 'restart' apache24 because apache24_enable is NO.
Oct 26 13:57:33 duarte notifier: apache24 not running? (check /var/run/httpd.pid).
Oct 26 13:57:33 duarte notifier: Will not 'restart' apache24 because apache24_enable is NO.
Oct 26 13:59:25 duarte notifier: apache24 not running? (check /var/run/httpd.pid).
Oct 26 13:59:25 duarte notifier: Will not 'restart' apache24 because apache24_enable is NO.
Oct 26 14:00:00 duarte syslog-ng[1543]: Configuration reload request received, reloading configuration;
Oct 26 14:03:51 duarte notifier: apache24 not running? (check /var/run/httpd.pid).
Oct 26 14:03:52 duarte notifier: Will not 'restart' apache24 because apache24_enable is NO.

 

[Ismael Duarte]

Finally, got it to work.
Now, me being newbie, can't find what's the advantage to cifs. I've mapped a folder to "My Computer" and can use it, like with others shares with cifs.

 

[jkh]

Finally, got it to work.
Now, me being newbie, can't find what's the advantage to cifs. I've mapped a folder to "My Computer" and can use it, like with others shares with cifs.

The point is interoperability. You can't map CIFS shares to your phone or tablet. You can with WebDAV. Other systems might speak only NFS and not CIFS, in which case you want NFS. It's not a question of "advantage", it's a question of using whatever specific sharing protocol is most useful.

 

[cyberjock]

I've mapped CIFS to my phone.

 

[Smitterson]

The 2014-10-26 nightly seems to have fixed it. I've been using WebDAV via my phone (using Transmit) and it has been working great so far.

 

[camilo suarez]

interesting, is any benefit (performance wise) using webdav over cifs in a local network envarioment using windows?.

 

[Ismael Duarte]

upgraded to 9.3Beta.
Still can't turn off WebDav.
I was able to turn it on while in nightlies, but now it doesn't turn off.
Each time I try I see this in the Log

Code:

Nov 10 21:26:13 duarte notifier: apache24 not running? (check /var/run/httpd.pid).
Nov 10 21:26:14 duarte notifier: Will not 'restart' apache24 because apache24_enable is NO.

 

[Suraj Ravichandran]

EDIT: I earlier misread your question.

You can disable apache manually by running the following command:

Code:

service apache24 stop
Code:
 and then turn it off from the gui....Try this and see if it solves your problem.

 

[jkh]

Is there a bug here that WebDAV, once enabled, can never be turned back off though? :)

 

[Suraj Ravichandran]

@jkh I do not think so, unless some files were corrupted somehow.

I am using it and it is working fine (even tested it today before replying)

 

[Ismael Duarte]

Here is as I wrote. Can't solve.
I've made a clean install of 9.3, uploaded config and still doesn't turn off