Re: Locating appropriate packages for webapp install w/only FreeBSD or Debian package information
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Quoth Mike Burns <mike+open...@mike-burns.com>, on or about Sun, 3 Apr 2016 13:29:55 +0200: > On 2016-04-02 13.22.07 -0700, Damon Getsman wrote: > > Is there any method for locating these packages short of > > doing a search on each one of them and locating specific files > > and/or developer information? Just curious as to whether or not I [snip] > > http://www.openbsd.org/faq/faq15.html#PkgFind > > In short: > > pkg_locate > pkg_info -Q > grep -l SOME_FILE_NAME /usr/ports/*/*/pkg/PLIST Are pkg_locate and pkg_info -Q fairly interchangeable? I haven't used pkg_locate before and I'm afraid that it's not available on my system. I even checked the ports and packages for it. Wow I'm really ending up sounding more like a newbie here than I'd like, given how long I've been using the operating system. For instance, I'm currently trying to find where 'portmaster' will be available, referenced in the instructions I'm translating as being available in FreeBSD's ports at ports-mgmt/portmaster. While I can't use /usr/sbin/pkg_locate, I am noticing that there is a /usr/sbin/pkg_mklocatedb available, though I'm not sure how much good it'll do alone. :) The following 2 commands that you've given aren't turning up anything on the subject. Sorry if I'm missing anything really simple here. Any help is very much appreciated on this matter! -Damo iQIcBAEBAgAGBQJXAS1TAAoJECqJ6HQbyBt4a9cP/0eBMXV0+U0d/k3TNCzKLBtr qS8vLYq/wVyy7uah6BmmB9lPr4RMW8GUxX/+RME2Q1a6x0wKyjmiD9aIdM+0gZMw rc0otYTwPpcQr+41jTtG5L67JTUZI+WXvlq9Oah9SFuxNPqiot2b1chhedHlx4LN M1MtGW2pES14baufT8mt+hizjd2mzsouDTWVl5mP23b5Obkb7RsmsKInzWCCUiOl IpKwXSx1C/P6EtGqdPVJpYvZ10pkIHzJNOHNRriGPNDVCLi+JKyYZ/xdmmnbydyy pBtFu/7Bz1fCj2hDqLECW+2CAU7lsQzvfW8rxjOiyUHcUvaAIp6pQPwtHGmR+21V ZfzeVWhLlnGus+dHt+xYlJnIBJ4QmNpAr92V58NnbBzIjy7PbBbOKMOVAZl99wOw KAbCZoxbw/Sqvy5L1USDcdpC5dDXZAnSQ0Ilo1/M8lo2TwIV4wykoTHL+m/9MkjH WbbWFoWhTWawZmTRo5uT15GR3V9yg60m20GEmKPzmyh0JfGh+3ykHdJPAEVy57bF JwRwCT7OzsE3RwOOjmIwRFT8lDembl5eEgXZ2uY6G2bch25K+1YlgNcy8PWZehYH IN0M+8kiEhJDLEZw/S9D7pZWRZ8Tu7SfYNau/iyMcijYlHTRZoVuLB3SGItAgswb dz0LKNQTZaYiu1XafZEz =3cte -END PGP SIGNATURE-
Re: Locating appropriate packages for webapp install w/only FreeBSD or Debian package information
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Please completely ignore the previous email as I've become aware that this was, indeed, a foolishly simple problem. Looking for the other packages is being much more productive, being as they're not 'portmaster' which is the FreeBSD specific ports management utility, I guess. :P Oopsie. Still kind of wondering what's up with the lack of pkg_locate, though. -Damo Quoth Damon Getsman <damo.g...@gmail.com>, on or about Sun, 3 Apr 2016 07:48:50 -0700: > For instance, I'm currently trying to find where 'portmaster' will > be available, referenced in the instructions I'm translating as being > available in FreeBSD's ports at ports-mgmt/portmaster. While I can't > use /usr/sbin/pkg_locate, I am noticing that there is > a /usr/sbin/pkg_mklocatedb available, though I'm not sure how much > good it'll do alone. :) The following 2 commands that you've given > aren't turning up anything on the subject. > Sorry if I'm missing anything really simple here. Any help is very > much appreciated on this matter! iQIcBAEBAgAGBQJXAS6WAAoJECqJ6HQbyBt4Oj4P/2yklBq3GzpNBz1zbTFYeTL3 DURJnsdORMwGDi8mdRhV1Iepx0dgziJ8ocnmZgKUKz6mFdr9AD1Iic7a4dP/Obb7 aaYvpL0RHuW6ALoH7fUj/YIrP5H8KP9zgUKnZaB41hoERW/hix/XTjXBl3FtslvD 0aAI2M4pDP+7ritEdwGLEPYt3NhnCQgmwBZJUtPRULI0lDSZlqi0BWe5FzaXr2/5 fOl6EiJJu2r1U07vhtndw6CuMl5OZhatBW5gDS6457cbe9k/umr+nYbXPRWRb3In 6YKRF94i7OQ8teNBfXghEaeUAUOoWfweKDdusnLXpiFdFmvCEfdbVy+bsNOw2d1p 7DzEf2kM1WthZIWJfd0MANYE9C30Epgaw60KvWBIewUJXXR6wuBzdscamYNkZXPN sLjv0rY4hE7GV/uEVtB4xqKwoIkGObkIitd5sDtE32+5tuCVsA7uomoZq2r4p7ge yHWuWsb13dAfSTdCz+iptrfPN6GpVWQBo3dT/rNz8XGNJJ4/p+mbhRAz9ko/Cy5K 2DOSycBuHDWCuyKeTUYxtHyKOALfzV2qSdF9qGML0aZXx/Feny8ilDFG+GJBhB2v fJgPt8dtQ8IiorJcj6tTcFDlzvTgadXcQhMbaHKAsgPYPQOqaB74qdMAgSAD3hbz GMGodSfq3M9L4EnJ+wl2 =UPji -END PGP SIGNATURE-
Locating appropriate packages for webapp install w/only FreeBSD or Debian package information
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello. I am really wanting to write a guide to handling a semi-complicated install for a web app on obsd (diaspora*) but I'm a little bit hung up on locating some of the appropriate packages. Basically, I've got some fairly well proven installation instructions for various other OSes, for example Debian (or most other mainstream) linux, and FreeBSD. I've run into problems at the point of locating what packages will be necessary to install on an openbsd system to fill the same functionality. I was under a bit of a misconception that perhaps the package names, if not complete locations, would be close to the same as in FreeBSD. Is there any method for locating these packages short of doing a search on each one of them and locating specific files and/or developer information? Just curious as to whether or not I might not be in the loop for something that'll make life a lot simpler here. Thanks for any information. -D iQIcBAEBAgAGBQJXACnwAAoJECqJ6HQbyBt4w1wQAKbfRqcdmlAWBJmN4gd5rlpP n6iZFUIc8q4jRRSPAICDpruPUTA2lBZ67ZX1ZqH5Av9DarDMiYzPvrFJq/KTMwm/ yH+Yk2AJA8ez9oHEKjgPGfeGjS5QuByAZS/2k1hZaOpVFdTnnBVhSEBNcQq2+xMt 4y0tdxLTsFiXHezu2pRnWihVHOiStPqQvduDDlhzlmuz3OVh4KL28RLtaIArVbXW Ui7+kFovYG6sild7DB+cGyPipv12Z+2Ydp9PLuLwU21oDMbBOi+GO4YmF7WdCECj N/oWLwxUpk+w8wn+AoepSbAH50fz9cbN94J62MkhLF+P5hTD89zVSuWSG1ViDIBH kPknKaRmlbej4aYq5NNgj5ZeLHqtX7iO3Udwp1pw+q1NjvDY2ZwISmgUDQUdFNRv x5fClxJp9/HKheQIMCCQQVToVU9fApgXA1VU86FiYu/FShu32h1aVLOil1KlNjyN iJRpfY3OnnaSvtWdncpaeW91RZPmU0XxibkCUomyXtIKlYsH4a+pwKOTkAkFIsk/ 1PBp3NoYXqyLXgTzei0VDQ6b4sIIWgr8Ia62p7E6cFpwRi7G7cVSVzvlVDDo/sIf vizgdzpcxbFLr4CCCDyuCnMvNvCwEGuHe1dmkh+AVWYN/4HXCdMcHtUBv9+6tgqr XeuhS838GVlk5lKXR6df =QX56 -END PGP SIGNATURE-
Upgrade 5.6->5.7->5.8 broke claws-mail's GPG agent tie in
I have recently upgraded my OpenBSD server from 5.6 to 5.8 (following the appropriate procedure and not skipping upgrades, of course). Unfortunately, when I finished the 2 hops from 5.6 to 5.8, I realized that claws-mail was no longer able to access the GPG key agent (I think that's what it uses, my apologies if I'm using the wrong terminology) and had switched to using some console based passphrase dialog. This wouldn't be a problem except my OBSD machine runs headless. Most of its duties require no interaction, but I also use it for my secure communications box... This includes claws-mail and sending digitally clearsigned messages. Everything was working fine @ 5.6, the connections tunneled properly to ask for the key phrase before signing the message... Now, though, even if I don't background the process and leave it in control of the shell, typing the pass phrase isn't working. Ideally I'd like to get things back to the point where I'm able to have that tunneled GPG key agent ask me for the phrase and like actually work again... I'd settle for having to run claws-mail in the foreground and typing in the passphrase on console, too, if I absolutely had to, but I don't know what's going on with the inability to authenticate for the key there... Any helpful suggestions, pointers, intuition, anything, would be of great assistance here. Please let me know if you need any more information or facts surrounding the matter that I can supply to make this more useful. Thank you for your time and consideration on this matter! -Damo
Please disregard my last
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Of course, immediately after posting I finally stumbled across the right web hit: http://www.h-i-r.net/p/openbsd.html Please disregard my premature request for assistance. :) iQIcBAEBAgAGBQJUyxWxAAoJECqJ6HQbyBt4/goP/10yrYO+ViPbewYPjEBLrtiM kNwZUDTjWzDW94hz3sz7b+BsYFKYWXJofm5yTDMF0JvnuW7b9QNsyKF/DveFwo5d l2uuxxmCAX0fHt4uDwwsw/oC6+s6JnTg9kvOY+crIs5KsrQJJtEPKTlgxndzk5o/ J/PQ9KewwmPNGoQwMZ9fAc8ux0A6uuVKA9cMVju/7kvuZJYtOL9FFEXFwp5fvmzn jI9Q0efP6CxG8eW5Vu6aqBEECpSxGdWRjCRLKLXrqAshNkZmfjIaCPryR7aEOYg0 fILTTVSg9RPQDBvrf7yp4u+r6dYjJfMOcLrIcz9FMmc3eu8lx9Kw3c5hhXAzlOSA OdtdKJ41MIJxcicYdUAD0tEbxq9XdYxIHE3jldxkUo9a7KWIq0OvAtuoa+cv/ehJ E/xXcqNYqPQzZw8w8YQsJ9USB17wpnmsCRm5vElHNQ/2AGB3teVRM3OTxec8naV+ TtE732wmIE0D3r53dHm4rCIyRISnenVnOgRw7XrEn0+oGxUwJtZExGQugKJyN+9r uHxv3eGEElYEt74ThV9ff28+E67lyMXCuhpEnaXoVCkSb41N+dO5y9Td2eYQAArE IGymwCTbrxa1/tsPIh31PsSPjgtqQ7PzA8dlswPewAQMZ98rlzCOUk/que8h3uZG iShmuZ/Nyr64ZILWXhiJ =VHvP -END PGP SIGNATURE-
Re: Upgrading issues (i386 on PPro class) 5.4-5.5 leaving system horked
Hello everyone. I posted that information regarding the 5.4-5.5 upgrade breaking (and subsequent break when following someone's advice just to take it up to 5.6 since it was already horked like that) a few days back here. I was going to post some google groups and/or openbsd.org links to the previous threaded posts, but I'm not having luck digging them up on google groups, and it appears that majordomo on the openbsd.org site won't give summaries from previous months. Regardless, I just wanted to find out... I usually get people willing to give some advice, or at least willing to laugh and tell me the lesson that I needed to know on here. I was really kind of surprised that I haven't heard anything back on this for so long... So, can anybody tell me, is my situation just so hosed that it's helpless? I mean, should I stop waiting for potential ways to fix this dependency hosed box and reinstall and try to find a way to re-inject all of my data into it, or are the gurus just swamped with new years tasks? :) If any of you could give me some feedback I'd really appreciate it. Like I said with the issue when I was first mentioning it, this system is really integral to a lot of the work that I do, and it's my sole external facing server... It's like a knife in my gut not having it working. Anything is very much appreciated. Feel free to hit me up via personal email, too, if you'd rather avoid public posting for some reason. I hope you all have a better year than last. :) -Damon
Re: Upgrading issues (i386 on PPro class) 5.4-5.5 leaving system horked
From Nick Holland n...@holland-consulting.net Date Thu, 25 Dec 2014 22:52:15 -0500 My system won't run like 90% of the binaries on it. such as...? I'm assuming you mean add-on packages, not base utilities like tar or more. If more is screwed up, you didn't unpack in the right directory. My apologies for my lack of specific information. I was a wee bit flustered when this first happened. :) Your assumption is correct; base utilities were working correctly; I didn't notice any problems with anything in /bin or /sbin, but when I ventured outside of there I started finding more problems. This is user error. This upgrade *IS* trickier than most, but that's why we carefully document things -- if you follow the process, it works fine. I'm well aware of that. I've been using OpenBSD since 4.x, and a few times before that for brief stretches. After another response to my initial post I ended up tracing the problem down to /etc/pkg.conf and $PKG_PATH, both set for the entire system, pointing at irrelevant versions. One was pointing at a 5.4 repository and another was pointing at a 5.3 repository. That seems like a rather strange portion not to automate in the upgrade process, but I've hardly ever rolled a distribution of an OS before. Well, you didn't provide many details of what you actually did, but it is pretty obvious you did not uninstall all packages BEFORE you did the upgrade. Sucks to be you, but I bet you read the instructions more carefully next time. :) Good news, should be recoverable. The fact that you have binaries that don't run proves you didn't remove the packages before upgrade. The other options are your kernel and userland are out of sync (i.e., forgot to upgrade kernel or userland) or you unpacked your userland to a different location, but either of those would probably be far worse situations. Well I got a little slightly more detailed information on recovering from foolishness that I caused like this, and have implemented a recovery strategy to the best of my limited mindset. ;) Unfortunately, things are still out of sync a bit; everything, again, out of the primary /bin and /sbin directories, seems to pretty much be crashing on attempts to load invalid libraries. I'll consolidate the actual debugging output and facts of the matter into my reply to that message; if you're still willing to help, I certainly do appreciate your input on the problem. Should be posted within a relatively short amount of time here. Thank you for your time help on this matter. -Damon
Re: Upgrading issues (i386 on PPro class) 5.4-5.5 leaving system horked (now 5.4-5.6)
I then ran into a bunch that I had to install unsigned, finally just
hitting the 'a'll so as to stop having to manually intervene and say
'y'es on each one. These started with metaauto*, autoconf-2.69p0*,
bash-4.2.45, beave, and then I lost track of the rest with the 'a'll
install specified.
The 5.5 packages *are* signed.
Oh I know it. Wasn't really familiar enough with the internals to
the upgrade process to be able to locate where the problem was, but
with the following information that you gave me I was able to start
tracking things down. I actually made it from 5.5-5.6, when things
looked like they were doing alright, and I'd stripped down to the core
binaries, but once again I've got a seriously borked system at 5.6 now.
I think you are trying to update packages from an incorrect source.
Check that PKG_PATH in the environment and/or /etc/pkg.conf are valid
for 5.5 and do pkg_add -D installed -u to update everything (this
will reinstall all packages). Capture the output (e.g. with script) so
if it fails you can show the exact output.
So yeah, it very much looks like this is the issue that was causing so
much strife. I still don't know where it's originally coming from,
but /etc/pkg.conf had a 5.5 PKG_PATH line, and in the environment,
despite the fact that I've set my root .profile up to have PKG_PATH
exported to toronto's http server (and the correct 5.6 URI).
Once I had the package list saved, I went ahead and went through
with the upgrade to the 5.6 core system (which seemed to go without any
issues) before trying to upgrade the packages and then, in turn, the
ports (which I still haven't tried). Anyway, I'm still getting
borkage, and it's causing me great mental duress. I captured the
output of pkg_add -D installed -u (both stdout and stderr), along with
some other output along the way.
I'm afraid that I'm not very familiar with the actual OpenBSD system
at a core level, other than standard administration of services and
daemons; I hope that since I'm pretty sure this debugging information
will be deficient you guys can point me in the right direction of how
to help get you (and myself) more information. Unfortunately it seems
to be incidents like this that teach me the most about OSes; haven't
had to deal with it much with Linux, having started on Slackware back
in the 1.0.x kernel days, since my early 20s, but OpenBSD still kicks
me in the nads from time to time.
So anyway, here's what output I've got, and please ask for more if
it'll help, and thank you very much in advance. This machine is quite
vital to me and I'm very much hoping not to have to reinstall
everything from scratch and try to insert all of the information back
into the appropriate tables, services, etc, especially as some of them
are custom.
I am skipping the full package list and manual packages list, as I
don't _think_ they are needed; I'll get them to the list posthaste if
this is inaccurate.
-=-=-=-=-
Output of pkg_add -D installed -u (stderr):
ew package libxml-2.9.1p1 will run the following commands
+ @exec /usr/local/share/libxml2/rebuild
Running update
/usr/local/bin/xmlcatalog:/usr/lib/libiconv.so.6.0: undefined symbol
'__guard' /usr/local/bin/xmlcatalog:/usr/lib/libiconv.so.6.0: undefined
symbol '__guard' New package glib2-2.40.0p7 will run the following
commands
+
@exec /usr/local/bin/glib-compile-schemas /usr/local/share/glib-2.0/schemas
/dev/null
+ @exec /usr/local/bin/gio-querymodules /usr/local/lib/gio/modules
Running update
/usr/local/bin/glib-compile-schemas:/usr/lib/libiconv.so.6.0: undefined
symbol
'__guard' /usr/local/bin/gio-querymodules:/usr/lib/libiconv.so.6.0:
undefined symbol '__guard' New package shared-mime-info-1.3 will run
the following commands
+ @exec /usr/local/bin/update-mime-database /usr/local/share/mime
Running update
/usr/local/bin/update-mime-database:/usr/lib/libiconv.so.6.0: undefined
symbol '__guard' New package gdk-pixbuf-2.30.8 will run the following
commands
+ @exec /usr/local/bin/gdk-pixbuf-query-loaders --update-cache
Running update
/usr/local/bin/gdk-pixbuf-query-loaders:/usr/lib/libiconv.so.6.0:
undefined symbol '__guard' New package gtk-update-icon-cache-2.24.24
will run the following commands
+ @exec /usr/bin/find /usr/local/share/icons -type d -mindepth 1
-maxdepth 1 -exec /usr/local/bin/gtk-update-icon-cache -q -t -f {} \;
2/dev/null || true Running update New package djvulibre-3.5.25.3p0
2will run the following commands
+ @exec /usr/local/bin/gtk-update-icon-cache -q
-t /usr/local/share/icons/hicolor Running update
/usr/local/bin/gtk-update-icon-cache:/usr/lib/libiconv.so.6.0:
undefined symbol '__guard' New package dbus-1.8.6v0 will run the
following commands
+ @exec /usr/local/bin/dbus-uuidgen --ensure=/etc/machine-id
Running update
install-info: warning: no entries found for
`/usr/local/info/gdbm.info'; nothing deleted install-info: menu item
`gdbm_load' already exists, for file `(none)' New package pango-1.36.5
will run the
Upgrading issues (i386 on PPro class) 5.4-5.5 leaving system horked
Well, I've never cared much for the holidays... So I figured, while everybody else was busy with them, what a perfect time for me to take down my BBS and other services and upgrade the system at least from 5.4-5.5. I've done multiple upgrades in a day before when I've gotten behind like this, and they've never been much of a problem, though I've run into an issue here and there before. That was before I ran into the removal of packages and reinstallation process that is necessary for this upgrade. Right off the bat I got issues about 'Can't locate object method filter_obsolete via package OpenBSD::Quirks1 at /usr/libdata/perl5/OpenBSD/AddDelete.pm line 351'. This was at the 'final step', and there had been no hiccups during the sysmerging process that I wasn't used to. After this issue, I started having packages that the system was trying to reinstall but totally horked on. I'm not totally sure if this is comprehensive at this point, but here are the packages and what I had to do with them: * apcupsd - had to manually remove from pkg_list_manual * cups - ditto * fedora-base - ditto * ntop - ditto * hylafax smsmail or whatever - ditto I then ran into a bunch that I had to install unsigned, finally just hitting the 'a'll so as to stop having to manually intervene and say 'y'es on each one. These started with metaauto*, autoconf-2.69p0*, bash-4.2.45, beave, and then I lost track of the rest with the 'a'll install specified. My system won't run like 90% of the binaries on it. I have upgrades of my home directory, BBS directory, and SQL dumps of most everything except my most recent changes, but I'm really hoping to avoid that... Does anybody have any tips? Would an install over the top straight to 5.6 maybe work? I've never had the install process leave me with such a lobotomized system before. Usually it's just something like mediawiki not working with latex math markup any more or wordpress breaking. :( This is my primary server, and it pains me significantly to have it down, and I really love OpenBSD, despite the hiccups at times. Does anybody have any suggestions? Any help or pointers in the right direction would be greatly appreciated. Thanks in advance.
Re: Encrypted filesystem fscking -- 'fsck -c 2' using fsck from before release 5.0?
Thank you for the quick reply, Otto. I overlooked that option, which is kind of funny, I know it's saved my butt before. Anyway, I tried using alternate superblocks, several of them (picked at random from various spots within the ones named by newfs -N), and fsck is still dying with the same error message. I have been able to mount the filesystem read-only. I'm not sure what else to do at this point. I feel like I'm overlooking something really obvious and foolish, but I can't quite put my finger on it. Anybody have any other ideas? On Mon, Feb 10, 2014 at 7:38 AM, Otto Moerbeek o...@drijf.net wrote: I have an OpenBSD Virtual Machine (v.5.4) that, unfortunately, got shut down improperly the other day. This machine had a mounted partition /dev/rwd0j, which disklabel is reporting as a fstype of 4.2BSD (fsize 2048, bsize 16384, cgp 1). The partition is completely full with an encrypted filesystem image, which was mounted at the time of the evil shutdown. When I try to mount the (host [/dev/rwd0j]) partition, I receive an error telling me that the filesystem is not clean and I need to run fsck. When I manually run fsck, I am receiving an error that the 'version of filesystem is too old', and that I must update it to a more recent format with 'fsck -c 2', using a version of fsck that is from before release 5.0. Unfortunately, I have vital services on this virtual machine that I need to get running again as soon as possible for users other than myself. I have not been able to locate any archive with a binary version of fsck for i386 from a release of OpenBSD prior to 5.0, nor am I able to find any way around this, at least during the first few dozen times ramming my head into the brick wall here. I would very much appreciate any ideas that anybody might have in order to get this filesystem clean and running again asap. Likely you superblock is corrupted, giving a spurious error message concerning the fs version. Try using an alternate superblock, using the -b option (see man page).
Encrypted filesystem fscking -- 'fsck -c 2' using fsck from before release 5.0?
I have an OpenBSD Virtual Machine (v.5.4) that, unfortunately, got shut down improperly the other day. This machine had a mounted partition /dev/rwd0j, which disklabel is reporting as a fstype of 4.2BSD (fsize 2048, bsize 16384, cgp 1). The partition is completely full with an encrypted filesystem image, which was mounted at the time of the evil shutdown. When I try to mount the (host [/dev/rwd0j]) partition, I receive an error telling me that the filesystem is not clean and I need to run fsck. When I manually run fsck, I am receiving an error that the 'version of filesystem is too old', and that I must update it to a more recent format with 'fsck -c 2', using a version of fsck that is from before release 5.0. Unfortunately, I have vital services on this virtual machine that I need to get running again as soon as possible for users other than myself. I have not been able to locate any archive with a binary version of fsck for i386 from a release of OpenBSD prior to 5.0, nor am I able to find any way around this, at least during the first few dozen times ramming my head into the brick wall here. I would very much appreciate any ideas that anybody might have in order to get this filesystem clean and running again asap. Thank you muchly in advance!
Issues compiling binkd-1.1 on OpenBSD 5.3 (testing on 5.4 in a bit, as well); ns_msg undeclared
. ;) -Damon Getsman
Upgrade to 5.0 from 4.x broke Apache+PHP's ability to talk to mysql.sock
Whoops; sent this earlier, but I hadn't changed the message subject from the Message Digest default text. I assume that's why it wasn't forwarded previously. Here's what I'd written on this subject previously: Awhile back here, I brought up an issue that occurred when I was upgrading my system from OpenBSD 4.x to 5.0. I'm not sure if it was on this mailing list or not, but this seems like the most appropriate place to bring it up. I had relied on several services via Apache that utilize PHP MySQL in a fairly standard configuration. Unfortunately, when I upgraded (all according to the standard upgrade instructions provided), all of my services broke due to PHP not being able to connect to the sock located in '/var/run/mysql/mysql.sock'. I asked for help and googled like a fiend for awhile, but even when interactively talking to folks in freenet's #openbsd, I was unable to find what might've been wrong with this. Foolishly enough, several times I considered the fact that httpd would be executing everything in the chroot jail of '/var/www', but I didn't research it that deeply or try moving the sock, because I figured that with all of the people I spoke to already, certainly one of the experts would have mentioned if this had been causing an issue or not. Last night, however, when I decided to take another stab at things, googling turned up a result that I hadn't seen previously (I am google-tarded, so I will accept the possibility that I'd not done as straightforward an attempt to look for the answer of this issue as I'd thought). The link was at http://philihp.com/blog/2008/connecting-to-mysql-with-php-in-apache-on-openbsd/ (2008? Certainly I must not have googled as well as I thought!), and referred to a permanent (although kludgy) solution found at http://www.openbsdsupport.org/e107_CMS.html . The solution was, indeed, dealing with creating a hardlink to somewhere within the chroot'ed jail; in this case under /var/www/var/run/mysql/mysql.sock after the appropriate path was created. Anyway I just thought that I'd post that here, since a lot of people in the OpenBSD community didn't seem to know how simple the solution really was or where it might be found at. It might be a good idea to toss this in the 4.x to 5.0 upgrade instructions, as well. It seems like a relatively simple oversight. Best wishes. -Damon
Re: Weekly digest, Issue 1685 (81 messages)
Awhile back here, I brought up an issue that occurred when I was upgrading my system from OpenBSD 4.x to 5.0. I'm not sure if it was on this mailing list or not, but this seems like the most appropriate place to bring it up. I had relied on several services via Apache that utilize PHP MySQL in a fairly standard configuration. Unfortunately, when I upgraded (all according to the standard upgrade instructions provided), all of my services broke due to PHP not being able to connect to the sock located in '/var/run/mysql/mysql.sock'. I asked for help and googled like a fiend for awhile, but even when interactively talking to folks in freenet's #openbsd, I was unable to find what might've been wrong with this. Foolishly enough, several times I considered the fact that httpd would be executing everything in the chroot jail of '/var/www', but I didn't research it that deeply or try moving the sock, because I figured that with all of the people I spoke to already, certainly one of the experts would have mentioned if this had been causing an issue or not. Last night, however, when I decided to take another stab at things, googling turned up a result that I hadn't seen previously (I am google-tarded, so I will accept the possibility that I'd not done as straightforward an attempt to look for the answer of this issue as I'd thought). The link was at http://philihp.com/blog/2008/connecting-to-mysql-with-php-in-apache-on-openbsd/ (2008? Certainly I must not have googled as well as I thought!), and referred to a permanent (although kludgy) solution found at http://www.openbsdsupport.org/e107_CMS.html . The solution was, indeed, dealing with creating a hardlink to somewhere within the chroot'ed jail; in this case under /var/www/var/run/mysql/mysql.sock after the appropriate path was created. Anyway I just thought that I'd post that here, since a lot of people in the OpenBSD community didn't seem to know how simple the solution really was or where it might be found at. It might be a good idea to toss this in the 4.x to 5.0 upgrade instructions, as well. It seems like a relatively simple oversight. Best wishes. -Damon
Re: Problems w/apache+php+mysqld since 4.9-5.0 OpenBSD Upgrade
Sorry, had some guests over the weekend, and I was unable to continue with the thread for a bit. I hope you guys are willing to catch up where you left off, I still haven't been able to get apache+php+mysql working again on my server since the 4.9-5.0 upgrade, and I really need my wiki and other associated services here. Managed to get done with my speech without them, at least. *grin* Still really could've used the wiki for the reference gathering, though. Thankfully nobody asked me for references. So, here is the output from php -m: Mon May 27 20:01 contract:/home/ftp$ php -m [PHP Modules] bcmath calendar ctype date dom exif filter ftp gettext hash iconv json libxml mbstring mysql openssl pcre PDO posix Reflection session SimpleXML sockets SPL standard suhosin sysvmsg sysvsem sysvshm tokenizer wddx xml xmlreader xmlwriter zlib [Zend Modules] Suhosin -=-=-=-=- So it looks like at least from the command-line invoked php, things are loading the mysql version just fine. And I checked, yes, and mysqld is running via invocation of mysqld_safe. I'll post the appropriate snippets from all of the php*.ini files scattered about my installation in just a bit here as soon as I can gather them all together. A visitor has stopped by again, so I must take a brief respite. On Wed, May 22, 2013 at 7:18 PM, Richard Toohey richardtoo...@paradise.net.nz wrote: On 05/23/13 12:08, Damon Getsman wrote: Okay, now I've got the phpinfo output. Nothing is jumpin' out at me, if y'all care to take a look at it I've got it available at bismaninfo.hopto.org/debug.php for a limited time here. No mysql in the output. What does php -m give you, etc. It's like the message you are getting - something is up with the mysql extension in your install. Check the ini files, etc. You are using the base Apache and PHP is working - you need to look at the mysql extension and find out why it is not enabled or not loading.
Problems w/apache+php+mysqld since 4.9-5.0 OpenBSD Upgrade
Hello all, and thank you for taking the time to take a look at this issue that I am currently having. I've been a strong advocate of OpenBSD for some time, but have only recently taken steps to start upgrading some of my machines instead of reinstalling. My primary server was a 4.9 installation, and it was running apache, with PHP and MySQL integrated for the purpose of serving a mediawiki, a gallery2 installation, and a few other utilities that I have had up for myself and some friends. Unfortunately, ever since I've made the leap from 4.9 to 5.0, I've been unable to get anything other than plain HTML documents to display via apache. The server tells me that there are either '500' server errors or with a little more detail MediaWiki tells me (Can't contact the database server: MySQL functions missing, have you compiled PHP with the --with-mysql option? ). Now according to the pkg_info listing that I have, I _believe_ that I have all of the proper packages and libraries installed, but I guess I am mistaken as I'm still not able to serve pages up with any sort of MySQL back end handling. Here is the output of 'pkg_info -a -m' for anybody who cares to verify this: BitTorrent-4.4.0p10 cooperative file distribution system implemented in Python ImageMagick-6.6.6.10p0 image processing tools alacarte-0.12.4p7 easy GNOME menu editing tool apache-httpd-2.2.15p0 apache HTTP server apcupsd-3.14.8p2daemon for controlling APC UPSes archie-1.4.1Prospero client for the archie service bash-4.2.10 GNU Bourne Again Shell beav-1.40.15binary editor and viewer bzip2-1.0.6 block-sorting file compressor, unencumbered calc-2.11.7 C-style arbitrary precision calculator camlimages-3.0.2p0 image manipulation functions for Objective Caml check_bioctl-1.9Nagios plugin to check RAID status with bioctl check_email_delivery-0.7.0 Nagios plugin to check full email delivery loop (SMTP /IMAP) check_hw_sensors-1.42 Nagios plugin to monitor sysctl hw.sensors check_mssql_health-1.5.3 Nagios plugin to check Microsoft SQL Server check_openbgpd-1.5 Nagios plugin to monitor OpenBGPd peers cups-1.4.7p0Common Unix Printing System cups-pdf-2.5.1 PDF backend for CUPS curl-7.21.7 get files from FTP, Gopher, HTTP or HTTPS servers dosbox-0.74p0 x86 with DOS emulator targeted at playing games emacs-22.3p10 GNU editor: extensible, customizable, self-documenting fedora_base-4.0p8 Linux compatibility package based on Fedora Core 4 firefox-5.0p3 Mozilla web browser firefox35-3.5.19p2 Mozilla web browser ghostview-1.5p3 X11 front-end for ghostscript git-1.7.6p0 GIT - Tree History Storage Tool git-svn-1.7.6p0 GIT - subversion interoperability tools git-x11-1.7.6p0 GIT - graphical tools gnome-common-2.34.0 common automake macros for GNOME gnome-desktop-2.32.1p4 components for the GNOME desktop gnome-mplayer-1.0.4p1 GTK+/GNOME frontend for MPlayer gnome-panel-2.32.1p5 GNOME panel gnome-screensaver-2.30.2p2 screen saver and locker for GNOME gnome-system-monitor-2.28.2p6 sytem monitor for GNOME gnome-system-tools-2.32.0p6 sytem configuration GUI for desktops gnuchess-5.08 chess program gpgme-1.1.5p1 GnuPG Made Easy gstoraster-1.03p0 filter to convert PostScript or PDF to cups raster format ircII-20081115p0Internet Relay Chat client ispell-3.2.06p6 interactive spelling checker jove-4.16p1 Jonathan's Own Version of Emacs kdebase-3.5.10p13 K Desktop Environment, basic applications kermit-8.0.211 serial and network communications package latex-mk-1.9.1p0set of Makefile fragments to manage LaTeX documents libpurple-2.9.0 multi-protocol instant messaging library libreoffice-3.4.1.3p1v0 multi-platform productivity suite mediawiki-1.15.5p3 web-based collaborative editing environment minicom-2.2p0 MS-DOS Telix-like serial communication program mpg123-1.13.1 fast console MPEG audio player and decoder library mrtg-2.17.1p1 multi-router traffic grapher mutt-1.5.21v0-sasl tty-based e-mail client, development version mysql-server-5.1.54p9 multithreaded SQL database (server) ncftp-3.2.3 ftp replacement with advanced user interface nethack-3.4.3p4-qt dungeon explorin', hackin', game. Piece of cake nmap-5.51p0 scan ports and fingerprint stack of network hosts ntop-1.1network usage, interface similar to top(1) ntp-4.2.6pl2p7 Network Time Protocol reference implementation ocaml-3.12.0p0 ML language based on complete class-based objective system oinkmaster-2.0p0update your Snort rules p7zip-9.20.1file archiver with high compression ratio partial-wordpress-3.0.2 standard compliant weblog pgp-2.6.3 Pretty Good Privacy 2.6.3ia php-5.2.17p5server-side HTML-embedded scripting language php-curl-5.2.17p3 curl URL library extensions for php5 php-gd-5.2.17p4 image manipulation extensions for php5 php-imap-5.2.17p3 imap, pop3 and nntp
Re: Problems w/apache+php+mysqld since 4.9-5.0 OpenBSD Upgrade
Richard: Not sure if I'm using the base apache or 2.2. Here's what httpd -V is showing me: Wed May 22 17:50 contract:~$ httpd -V Server version: Apache/1.3.29 (Unix) Server's Module Magic Number: 19990320:15 Server compiled with -D EAPI -D HAVE_MMAP -D HAVE_SHMGET -D USE_MMAP_SCOREBOARD -D USE_MMAP_FILES -D HAVE_FLOCK_SERIALIZED_ACCEPT -D HAVE_SYSVSEM_SERIALIZED_ACCEPT -D SINGLE_LISTEN_UNSERIALIZED_ACCEPT -D DYNAMIC_MODULE_LIMIT=64 -D HARD_SERVER_LIMIT=256 -D HTTPD_ROOT=/var/www -D SUEXEC_BIN=/usr/sbin/suexec -D DEFAULT_PIDLOG=logs/httpd.pid -D DEFAULT_SCOREBOARD=logs/httpd.scoreboard -D DEFAULT_LOCKFILE=logs/httpd.lock -D DEFAULT_ERRORLOG=logs/error_log -D TYPES_CONFIG_FILE=conf/mime.types -D SERVER_CONFIG_FILE=conf/httpd.conf -D ACCESS_CONFIG_FILE=conf/access.conf -D RESOURCE_CONFIG_FILE=conf/srm.conf I stopped at 5.0 because I figured that if I was having problems at this point pushing it further might create more until I get them resolved. If I'm wrong about that I'll certainly push it up to 5.3. I've got another machine here that I've installed 5.2 on recently, I'll take that one up to 5.3 just to get used to it (it's not a server machine). I do understand the 'chroot' concept, not sure how exactly it's applicable in this case; despite the fact that I believe httpd is chrooted to /var/www, I do know that php exists under this tree in its /usr/local/bin and the libphp5 file exists there where it should as well, I believe. I have also bumped up the php error reporting but I can't seem to find much about it in the applicable logfiles (/var/log/messages, /var/www/logs/error_log, etc). Truncating the previous discussion as I'm assuming that you've got logs of what's going on here. Thank you for the help!
Re: Problems w/apache+php+mysqld since 4.9-5.0 OpenBSD Upgrade
Bryan, after doing that it appears that it's not even getting executed. I put the script into a web accessible file called debug.php, loaded it in my browser and saw a blank page. Viewing the source is showing the original ? phpinfo(); ?, leading me to believe that it is not even handing it off to the appropriate script engine... Not sure if I'm right but does that help at all?
Re: Problems w/apache+php+mysqld since 4.9-5.0 OpenBSD Upgrade
And, um, wrapping the snippet in the appropriate html head/head body? phpinfo(); ?/body /html didn't seem to help matters at all, either. :(
Re: Problems w/apache+php+mysqld since 4.9-5.0 OpenBSD Upgrade
Nope, I caught the PHP upgrade instructions and I believe they've been carried out correctly. :(
Re: Problems w/apache+php+mysqld since 4.9-5.0 OpenBSD Upgrade
Okay, now I've got the phpinfo output. Nothing is jumpin' out at me, if y'all care to take a look at it I've got it available at bismaninfo.hopto.org/debug.php for a limited time here.
ext42fs support?
I've been looking through the FAQs and some on the forums, and I've come up with the conclusion that I'm not able to mount a linux ext4fs partition on my OpenBSD 4.9 system due to the fact that ext4fs isn't supported [allegedly]. I've even tried using MAKEDEV to rebuild the device /dev/wd1i and /dev/rwd1i to no avail. I still get the issue that a block device is required. Disklabel, of course, shows the partition as being there and being ext2fs. Anyway, if I'm correct in all of those assumptions, I guess what I'm wondering is if there are any other utilities for [at least] reading an ext4fs. I've got several terrabytes of information that I'd really like to at least be able to serve to the other machines on my network from this machine. If there are not, are there plans for adding this support in the near future at all? Thanks again! -Damon Getsman
Re: Reconfiguration for 'chrome' browser broke login capability
Alright, so restoring the contents of /etc/login.conf has, indeed, fixed my ability to login via whatever means and use sudo. Quite honestly I don't know how all of those lines got deleted from it, unless I left it open in vim and the cat jumped on the keyboard while I was out for a little bit or something. Anyway, now that I restored it and everything is working, I again attempted to follow these instructions given when starting up chrome: -=-=-=-=-=- You should make the following changes for your login class in /etc/login.conf (you will need to logout and login for these to take effect). - increase datasize-max to at least 716800. - increase openfiles-max to at least 400. -=-=-=-=-=- Which results in the follow /etc/login.conf file: -=-=-=-=-=- default:\ :path=/usr/bin /bin /usr/sbin /sbin /usr/X11R6/bin /usr/local/bin:\ :umask=022:\ #:datasize-max=512M:\ :datasize-max=716800:\ :datasize-cur=512M:\ :maxproc-max=256:\ :maxproc-cur=128:\ :openfiles-cur=128:\ :openfiles-max=400:\ :stacksize-cur=4M:\ :localcipher=blowfish,6:\ :ypcipher=old:\ :tc=auth-defaults:\ :tc=auth-ftp-defaults: # # Settings used by /etc/rc and root # This must be set properly for daemons started as root by inetd as well. # Be sure reset these values back to system defaults in the default class! # daemon:\ :ignorenologin:\ :datasize=infinity:\ :maxproc=infinity:\ :openfiles-cur=128:\ :stacksize-cur=8M:\ :localcipher=blowfish,8:\ :tc=default: # # Staff have fewer restrictions and can login even when nologins are set. # staff:\ :datasize-cur=512M:\ :datasize-max=infinity:\ :maxproc-max=512:\ :maxproc-cur=128:\ :ignorenologin:\ :requirehome@:\ :tc=default: # # Authpf accounts get a special motd and shell # authpf:\ :welcome=/etc/motd.authpf:\ :shell=/usr/sbin/authpf:\ :tc=default: -=-=-=-=-=-=- (with the comments at the beginning removed in order to save cutting pasting) Anyway, despite the changes that I've made in datasize-max and the addition of the openfiles-max setting, I'm still receiving the error message from chrome and unable to use it properly due to too many open temp files. Anybody have any suggestions for me or any input on whether or not I modified /etc/login.conf properly? Much appreciated. -Damon Getsman
Reconfiguration for 'chrome' browser broke login capability
Yesterday I was attempting the reconfiguration that the 'chrome' browser recommends in order for using it effectively in OpenBSD 4.9. Namely, I attempted to follow the following instructions: -=-=-=-=-=- You should make the following changes for your login class in /etc/login.conf (you will need to logout and login for these to take effect). - increase datasize-max to at least 716800. - increase openfiles-max to at least 400. Do you want to run Chromium anyway? (If you don't increase these limits, Chromium might fail to work properly.) -=-=-=-=-=- After the changes, the following is what I ended up with in my /etc/login.conf: -=-=-=-=-=- contract:~$ cat /etc/login.conf #datasize-max=768M:\ datasize-max=716800: :datasize-cur=512M:\ :maxproc-max=256:\ :maxproc-cur=128:\ :openfiles-cur=128:\ :stacksize-cur=4M:\ :localcipher=blowfish,6:\ :ypcipher=old:\ :tc=auth-defaults:\ :tc=auth-ftp-defaults:\ :openfiles-max=400: # # Settings used by /etc/rc and root # This must be set properly for daemons started as root by inetd as well. # Be sure reset these values back to system defaults in the default class! # daemon:\ :ignorenologin:\ :datasize=infinity:\ :maxproc=infinity:\ :openfiles-cur=128:\ :stacksize-cur=8M:\ :localcipher=blowfish,8:\ :tc=default: # # Staff have fewer restrictions and can login even when nologins are set. # staff:\ :datasize-cur=512M:\ :datasize-max=infinity:\ :maxproc-max=512:\ :maxproc-cur=128:\ :ignorenologin:\ :requirehome@:\ :tc=default: # # Authpf accounts get a special motd and shell # authpf:\ :welcome=/etc/motd.authpf:\ :shell=/usr/sbin/authpf:\ :tc=default: -=-=-=-=-=- After making the preceding changes, I attempted to log in on a console tty and ended up with a 'failure to retrieve default class' at the login: prompt immediately after entering my login name. Logins by ssh, as well, are not working, although it fails through a different set of steps; mainly, public-key authentication fails, and then the password is not recognized at the failthrough password prompt. As I am sure you can understand, I would like to be able to login to my machine, especially before there is a power outage or some other cause that forces me to reboot at which point I can only assume I will be locked out of the machine and that it will be even more difficult to recover from. I am also eager to have 'chrome' working correctly, but I assure you that is a distant second at this point. Can anybody help me with some steps that can return login functionality to this machine and possibly even help me make the configuration changes that chrome was talking about in a manner that doesn't make my machine impossible to log in to? Thank you very much in advance. Also, the last few thousand lines of my /var/log/messages contains the following if this is helpful at all: -=-=-=-=-=- Aug 19 00:31:21 contract inetd[21573]: /usr/libexec/comsat: exit status 1 Aug 19 00:31:21 contract inetd[13153]: daemon: couldn't resolve 'tc' Aug 19 00:31:21 contract inetd[13153]: comsat/udp: setusercontext: No such file or directory Aug 19 00:31:21 contract inetd[21573]: /usr/libexec/comsat: exit status 1 Aug 19 00:31:21 contract inetd[22957]: daemon: couldn't resolve 'tc' Aug 19 00:31:21 contract inetd[22957]: comsat/udp: setusercontext: No such file or directory Aug 19 00:31:21 contract inetd[21573]: /usr/libexec/comsat: exit status 1 Aug 19 00:31:21 contract inetd[4550]: daemon: couldn't resolve 'tc' Aug 19 00:31:21 contract inetd[4550]: comsat/udp: setusercontext: No such file or directory Aug 19 00:31:21 contract inetd[21573]: /usr/libexec/comsat: exit status 1 Aug 19 00:31:21 contract inetd[21573]: comsat/udp server failing (looping), service terminated Aug 19 07:32:56 contract sshd: staff: couldn't resolve 'tc' Aug 19 07:32:56 contract sshd: staff: couldn't resolve 'tc' Aug 19 07:32:59 contract sshd: default: unknown class Aug 19 07:33:19 contract last message repeated 2 times -=-=-=-=-=- Thanks again. -Damon Getsman P.S. I noted the lack of a \ at the end of the first line of my /etc/login.conf after typing this message. Unable to sudo, as well, I switched to a console that was already sudo su'ed, and added that backslash. I am still receiving the same errors.
