Re: 500 httpd error with owncloud
File permissions should be ok, I changed the ownership of /var/www/owncloud and owncloud-data to www:www, no change whatsoever. It must be something with owncloud, because when I am not logged in, I can see the owncloud login screen just fine. Furthermore, a phpinfo() page works, too. But when I log in with a correct username and password, I get the 500 error. I already ran the server in the foreground, with increased verbosity. It only gives an unspecific error: default 192.168.178.18 - - [29/Dec/2014:16:58:15 +0100] GET /owncloud/index.php/apps/files/ HTTP/1.1 500 0 server default, client 5 (1 active), 192.168.178.18:54562 - 192.168.178.49, /owncloud/index.php/apps/files/ (500 Internal Server Error) Clemens On 29.12.14 16:42, mario wrote: Sqlite3 is is fine. As I said I use it. What about file permissions? Maybe run the httpd daemon in the foreground and increase its verbosity. Did you manage to run a simple perl or bash script through 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 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 00b498e42000 rlib 01 0 /usr/lib/libedit.so.5.1 00b430ec9000 00b431323000 rlib 01 0 /usr/lib/libcurses.so.14.0 00b472f65000 00b473377000 rlib 02 0 /usr/lib/libpthread.so.18.1 00b497b7e000 00b49806a000 rlib 01 0 /usr/lib/libc.so.78.0 00b44840 00b44840 rtld 01 0 /usr/libexec/ld.so I copied all libraries used by sqlite3 in the folder /var/www/usr/lib/: $ ls -lh /var/www/usr/lib/ total 17920 -r--r--r-- 1 root daemon 3.2M Dec 29 09:01 libc.so.78.0 -r--r--r-- 1 root daemon 1.4M Dec 29 09:01 libcurses.so.14.0 -r--r--r-- 1 root daemon 480K Dec 29 09:01 libedit.so.5.1 -r--r--r-- 1 root daemon 208K Dec 29 09:01 libpthread.so.18.1 -r--r--r-- 1 root daemon 3.4M Dec 29 09:01 libsqlite3.so.28.0 I think it has something to do with sqlite3 - this is just a guess. Trying to install wordpress form ports, it failed at the database setup (although wp uses mariadb/mysql). Has anyone else experienced such problems? Clemens
Re: 500 httpd error with owncloud
Hey,
Since your initial email you have not included any config files, i.e.
httpd.conf, etc. Would you, perhaps, care to share them with us? My
shew stone is being serviced.
Of course. Here they are:
# cat /etc/httpd.conf
server default {
listen on wpi0 port 80
directory { no index, index index.php }
location *.php {
fastcgi socket /run/php-fpm.sock
}
}
types {
include /usr/share/misc/mime.types
}
/etc/php-5.5.ini: everything default except the values mentioned in the
pkg-readme of owncloud:
allow_url_fopen = On
memory_limit = 512M
upload_max_filesize = 1024M # to accept large files upload
post_max_size = 1030M# sync with above value
all other php module config files unchanged, and active according to
phpinfo().
# cat /var/www/owncloud/config/config.php
?php
$CONFIG = array (
'instanceid' = 'MY_ID',
'passwordsalt' = 'MY_PW-SALT',
'secret' = 'MY_SECRECT',
'trusted_domains' =
array (
0 = '192.168.178.49',
),
'datadirectory' = '/owncloud-data',
'overwrite.cli.url' = 'http://192.168.178.49/owncloud',
'dbtype' = 'sqlite3',
'version' = '7.0.4.2',
'dbname' = 'owncloud_db',
'dbhost' = '127.0.0.1',
'dbtableprefix' = 'oc_',
'dbuser' = 'oc_clemens',
'dbpassword' = 'MY_DB-PASSWORD',
'installed' = true,
);
change in /etc/my.conf as described in the mariadb pkg-readme (I did not
manage to use MariaDB with owncloud or wordpress yet):
chrooted daemons and MariaDB socket
===
For external program running under a chroot(8) to be able to access the
MariaDB server without using a network connection, the socket must be
placed inside the chroot.
e.g. httpd(8) or nginx(8): connecting to MariaDB from PHP
-
Create a directory for the MariaDB socket:
# install -d -m 0711 -o _mysql -g _mysql /var/www/var/run/mysql
Adjust /etc/my.cnf to put and connect to the MariaDB socket
within the chroot:
[client]
socket = /var/www/var/run/mysql/mysql.sock
[mysqld]
socket = /var/www/var/run/mysql/mysql.sock
If I missed a config file, let me know!
Clemens
Re: 500 httpd error with owncloud
Reading the recent post on misc, Best way forward w.r.t.
apache/nginx/httpd?, I don't think httpd is ready for owncloud,
especially for someone with little experience running web servers.
Anyway, thanks guys for your support.
Clemens
On 30.12.14 08:03, Jona Joachim wrote:
[This message has also been posted to gmane.os.openbsd.misc.]
On 2014-12-29, Clemens Gößnitzer e1126...@student.tuwien.ac.at wrote:
Hey,
Since your initial email you have not included any config files, i.e.
httpd.conf, etc. Would you, perhaps, care to share them with us? My
shew stone is being serviced.
Of course. Here they are:
# cat /etc/httpd.conf
server default {
listen on wpi0 port 80
directory { no index, index index.php }
location *.php {
fastcgi socket /run/php-fpm.sock
}
}
types {
include /usr/share/misc/mime.types
}
/etc/php-5.5.ini: everything default except the values mentioned in the
pkg-readme of owncloud:
allow_url_fopen = On
memory_limit = 512M
upload_max_filesize = 1024M # to accept large files upload
post_max_size = 1030M# sync with above value
all other php module config files unchanged, and active according to
phpinfo().
# cat /var/www/owncloud/config/config.php
?php
$CONFIG = array (
'instanceid' = 'MY_ID',
'passwordsalt' = 'MY_PW-SALT',
'secret' = 'MY_SECRECT',
'trusted_domains' =
array (
0 = '192.168.178.49',
),
'datadirectory' = '/owncloud-data',
'overwrite.cli.url' = 'http://192.168.178.49/owncloud',
'dbtype' = 'sqlite3',
'version' = '7.0.4.2',
'dbname' = 'owncloud_db',
'dbhost' = '127.0.0.1',
'dbtableprefix' = 'oc_',
'dbuser' = 'oc_clemens',
'dbpassword' = 'MY_DB-PASSWORD',
'installed' = true,
);
Was the sqlite database created? 'installed = true' means that it
assumes that the database is functional and it will not be initialized.
Also you will not need the hostname, user, db prefix, etc. with sqlite.
Also make sure that you don't need any url rewrites. I'm using
owncloud-6.0.4 and the documentation recommends url rewrites which are
not mandatory for owncloud to work but perhaps this changed in the new
version. Perhaps you should try with nginx and the recommended
configuration and see if it works and then go back to httpd.
Best regards,
Jona
Re: problems with run wirless driver
On 5 Jan 2015 22:21, Stefan Sperling s...@stsp.name wrote: Hmm, that makes a driver bug more likely. Can you try with FreeBSD? Their driver has essentially become the upstream version of run(4). If their driver works better we might be able to fix ours. Yes I will, but on Satuarday the earliest. I will let you know what the FreeBSD run driver does.
poster for 6.3
Will there be a poster for OpenBSD 6.3? Or is it possible to get the high-resolution image of https://www.openbsd.org/images/Harry.gif? And maybe even for 6.1? I still have some doors left for great OpenBSD posters :) Thanks again for a great new version! Donation will be on its way :) Clemens
Re: setting up an email server in a recent version of OpenBSD
On 27/09/2021 19:42, Teno Deuter wrote: Dear group, anyone could point to some recent online resources how to setup an email server in OpenBSD? What I found from Google was a bit thin. So I'm wondering if I was missing something out there. Thank you for your support Check out this from Gilles, one of the original developers of OpenSMTP: https://poolp.org/posts/2019-09-14/setting-up-a-mail-server-with-opensmtpd-dovecot-and-rspamd/
Updating nextcloud to new major version
When I try to update nextcloud to the next major version, it would not let me easily: # pkg_add -vi nextcloud Update candidates: quirks-5.5 -> quirks-5.5 quirks-5.5 signed on 2022-05-12T23:37:02Z Ambiguous: choose package for nextcloud a 0: 1: nextcloud-21.0.8p0 2: nextcloud-22.2.6 3: nextcloud-23.0.3 Your choice: 3 Can't install nextcloud-23.0.3 because of conflicts (nextcloud-22.2.6) --- nextcloud-23.0.3 --- Can't install nextcloud-23.0.3: conflicts Couldn't install nextcloud-23.0.3 Is there a way to do this upgrade without pkg_delete nextcloud && pkg_install nextcloud? Thanks.
Re: Updating nextcloud to new major version
On Fri, 2022-05-13 at 11:05 -0700, Courtney wrote: > Have you tried pkg_add -Uu? That did not do the trick... Thanks for the suggestion. > > Courtney > > On 5/13/22 10:35, Clemens Gößnitzer wrote: > > When I try to update nextcloud to the next major version, it would > > not > > let me easily: > > > > # pkg_add -vi nextcloud > > Update candidates: quirks-5.5 -> quirks-5.5 > > quirks-5.5 signed on 2022-05-12T23:37:02Z > > Ambiguous: choose package for nextcloud > > a 0: > > 1: nextcloud-21.0.8p0 > > 2: nextcloud-22.2.6 > > 3: nextcloud-23.0.3 > > Your choice: 3 > > Can't install nextcloud-23.0.3 because of conflicts (nextcloud- > > 22.2.6) > > --- nextcloud-23.0.3 --- > > Can't install nextcloud-23.0.3: conflicts > > Couldn't install nextcloud-23.0.3 > > > > > > Is there a way to do this upgrade without pkg_delete nextcloud && > > pkg_install nextcloud? > > > > Thanks. > > >
Re: Updating nextcloud to new major version
On Fri, 2022-05-13 at 20:58 +0200, Florian Obser wrote: > On 2022-05-13 19:35 +02, Clemens Gößnitzer > wrote: > > When I try to update nextcloud to the next major version, it would > > not > > let me easily: > > > > # pkg_add -vi nextcloud > > Update candidates: quirks-5.5 -> quirks-5.5 > > quirks-5.5 signed on 2022-05-12T23:37:02Z > > Ambiguous: choose package for nextcloud > > a 0: > > 1: nextcloud-21.0.8p0 > > 2: nextcloud-22.2.6 > > 3: nextcloud-23.0.3 > > Your choice: 3 > > Can't install nextcloud-23.0.3 because of conflicts (nextcloud- > > 22.2.6) > > --- nextcloud-23.0.3 --- > > Can't install nextcloud-23.0.3: conflicts > > Couldn't install nextcloud-23.0.3 > > > > > > Is there a way to do this upgrade without pkg_delete nextcloud && > > pkg_install nextcloud? > > pkg_add -r nextcloud That worked. Thanks! > > worked for me. > > > > > Thanks. > > >
