Custom CD mixes
If I wanna pull the music off CDs and make a custom album, is there a package that would allow me to choose the songs, and play order?
Re: pkgin does not install anything after upgrade to 9.2
Boot to single user and full fsck. Also make the backups you have been meaning to get around to right away
Re: pkgin does not install anything after upgrade to 9.2
Hi Greg, Thanks for your suggestions! It indeed seems to be corrupted :( I tried to nuke (rm -rf) the directory /usr/pkg/pkgdb/p5-Net-SSLeay-1.88nb1 but I got back that the directory is not empty which is pretty unusual for rm -rf. Now, when I try to list its contents, three files are shown: +COMMENT, +CONTENTS, +DESCR However, when listing with ls -al, I get the error: ls: +COMMENT: No such file or directory ls: +CONTENTS: No such file or directory ls: +DESCR: No such file or directory I tried to execute fsck for the node number (fsck 35752122) of the directory but I got back: fsck: cannot open '/dev/35752122': No such file or directory Is there any solution for this? Best regards, r0ller On 7/8/21 7:26 PM, Greg Troxel wrote: r0ller writes: The only error I see in pkg_install-err.log (which is not shown as error) which seems to block each pkg install is: pkg_admin: Cannot read +CONTENTS of package p5-Net-SSLeay-1.88nb1 Does anyone have any hint? pkg_admin rebuild-tree pkg_admin check make sure your variables in mk.conf are set to point to your pkgdb. See https://www.pkgsrc.org/pkgdb-change/ and set the variables even if you think it's not necessary. look in /usr/pkg/pkgdb/p5-Net-SSLeay-1.88nb1 and see if there is indeed no +CONTENTS. If true, you have had some corruption and I would rm -rf the p5-Net-SSLeay-1.88nb1 directory, and then you'll have to reinstall it.
ENOMEM during import with mariadb-10.5
Hello I encountered this problem with MariaDB 10.5 and I assumed someone could be interested by the workaround: when importing a large dump, it fails and /var/log/mariadb/error.log says: 2021-07-08 14:59:51 4 [ERROR] InnoDB: Unable to lock ./foo/bar.ibd error: 12 2021-07-08 14:59:51 4 [ERROR] InnoDB: Operating system error number 12 in a file operation. 2021-07-08 14:59:51 4 [ERROR] InnoDB: Error number 12 means 'Cannot allocate memory' 2021-07-08 14:59:51 4 [Note] InnoDB: Some operating system error numbers are described at https://mariadb.com/kb/en/library/operating-system-error-codes/ The error is misleading, and increasing memory limits will not help. ktrace shows that errno 12 (ENOMEM) is returned by a fcntl() call. Reading kernel sources shows it comes from lf_advlock() after lf_alloc() failed because (1) user is not root and (2) per-user lock limit has been reached. The per-user lock limit value is in the maxlocksperuid kernel variable, with a default value of 1024. It can be changed by patching the sources and rebuilding, or by patching the binary with gdb and rebooting, or by patching the loaded kernel in memory: echo "write maxlocksperuid 0x800"|crash -w Obviously it would be nicer if a sysctl existed for that, but at least you have a workaround to save your day if your import fail after an upgrade. -- Emmanuel Dreyfus m...@netbsd.org
