500 httpd error with owncloud

2014-12-28 Thread Clemens Goessnitzer
Hello everyone, I installed the owncloud server from ports, and tried to get it running with the new httpd. Unfortunately, I get a 500 Internal Server Error once I log in. However, the login page is shown perfectly fine. Here is the server log, when I run the server in debug/verbose mode

Re: 500 httpd error with owncloud

2014-12-28 Thread Clemens Goessnitzer
What do you have in /var/www/usr/lib # ls -la /var/www/usr/ total 16 drwxr-xr-x 4 root daemon 512 Dec 28 21:55 . drwxr-xr-x 14 root daemon 512 Dec 28 20:59 .. drwxr-xr-x 2 root daemon 512 Dec 26 23:29 sbin drwxr-xr-x 3 root daemon 512 Dec 28 20:47 share No such directory. I

Re: 500 httpd error with owncloud

2014-12-29 Thread Clemens Goessnitzer
$ ldd /usr/bin/sqlite3 /usr/bin/sqlite3: StartEnd Type Open Ref GrpRef Name 00b21e80 00b21ec11000 exe 10 0 /usr/bin/sqlite3 00b491c4e000 00b49212 rlib 01 0 /usr/lib/libsqlite3.so.28.0 00b498a0f000

Re: 500 httpd error with owncloud

2014-12-29 Thread Clemens Goessnitzer
the server? Sent from Samsung Mobile Original message From: Clemens Goessnitzer e1126...@student.tuwien.ac.at Date: 12-29-2014 04:12 (GMT-05:00) To: misc@openbsd.org Subject: Re: 500 httpd error with owncloud $ ldd /usr/bin/sqlite3 /usr/bin/sqlite3: StartEnd

Re: problems with run wirless driver

2015-01-05 Thread Clemens Goessnitzer
On 01/05/15 11:39, Stefan Sperling wrote: Try setting the AP to a 2.4 Ghz channel (1-13) and see if that improves things. 11a (5Ghz) has a shorter range than 11b/g. Still the same behavior. Could this be the APs fault? I am getting an Intel NUC soon and will set it up as an OpenBSD wireless

problems with run wirless driver

2015-01-05 Thread Clemens Goessnitzer
Hello everyone, I am running -current as of end-Decemberish. I am using a Ralink chip powered wireless adapter (chip: Ralink RT3052), which should be supported by the run driver. However, I get # sh /etc/netstart run0 run0: no link ... sleeping when I try to start the network (also

Re: problems with run wirless driver

2015-01-05 Thread Clemens Goessnitzer
Is your SSID hidden? I had the same problem on 5.6-stable when the SSID was hidden. Thankfully I could change the AP behaviour. No more problems since. hth No, not hidden, since this is absolutely useless.

Re: problems with run wirless driver

2015-01-05 Thread Clemens Goessnitzer
On 01/05/15 18:25, Stefan Sperling wrote: Not sure. Perhaps check if deactivating power-saving on the AP is possible. I don't believe the run(4) driver has support for it. Should be deactivated now. Can you share information shown in dmesg after 'ifconfig run0 debug' while you're using the

Re: problems with run wirless driver

2015-01-05 Thread Clemens Goessnitzer
On 01/05/15 19:43, Stefan Sperling wrote: This shows a scan. I don't see an association in there. You should also see WPA handshake on a successfull connect messages since your network uses WPA. In any case this should allow you to see exactly when the driver gets and drops link. These messages

pf, bridge and vether: interface with no group

2016-02-15 Thread Clemens Goessnitzer
Hello misc, I noticed a strange behaviour with pf, when having three interfaces connected with a bridge(4) device, where two are assigned to the group wlan and one to no group at all. I have two WLAN interfaces, athn0 and athn1, and three wired interfaces, re0 to re2. (re2 is not used ATM.) re0

Re: pf, bridge and vether: interface with no group

2016-02-16 Thread Clemens Goessnitzer
On 2016-02-16 11:17, Patrick Lamaiziere wrote: > Le Tue, 16 Feb 2016 00:10:41 +0100, > Clemens Goessnitzer <e1126...@student.tuwien.ac.at> a écrit >> Hello misc, > > Hi > Salut! > >> So, if I specify a group for re1, everything is working as expected

Re: pf, bridge and vether: interface with no group

2016-02-17 Thread Clemens Goessnitzer
On 2016-02-16 16:34, Patrick Lamaiziere wrote: > Le Tue, 16 Feb 2016 13:05:51 +0100, > Clemens Goessnitzer <e1126...@student.tuwien.ac.at> a écrit : > > Ok I think : > > the pf.conf rule > ### rules for internal network ### > pass inet proto { tcp, udp }