CURRENT on Solaris - another problem?
bill davidsen
davidsen at tmr.com
Wed Jan 28 17:23:32 UTC 2004
In article <20040127225611.GD22738 at virgin.gazeta.pl>,
=?iso-8859-2?Q?Przemys=B3aw?= Maciuszko <sal at agora.pl> wrote:
| Hi.
| I've just upgraded to latest CURRENT and i get the following in news.notice:
| Jan 27 23:54:00 inews nnrpd[8051]: [ID 223153 news.error] semop failed to
| getSharedLock: No space left on device
| Jan 27 23:54:00 inews nnrpd[8051]: [ID 745701 news.error] semop failed to
| release shared lock: Resource temporarily unavailable
| Jan 27 23:54:00 inews nnrpd[8051]: [ID 223153 news.error] semop failed to
| getSharedLock: No space left on device
| Jan 27 23:54:00 inews nnrpd[8051]: [ID 745701 news.error] semop failed to
| release shared lock: Resource temporarily unavailable
| Jan 27 23:54:00 inews nnrpd[8051]: [ID 223153 news.error] semop failed to
| getSharedLock: No space left on device
| Jan 27 23:54:00 inews nnrpd[8051]: [ID 745701 news.error] semop failed to
| release shared lock: Resource temporarily unavailable
"No space" seems pretty clear, what does 'df' tell you? Did you put
things in a bad place or leave some dirname unset? This could be an INN
bug, but the messages suggest you're out of space.
Or inodes, of course! Check that as well.
--
bill davidsen <davidsen at tmr.com>
CTO, TMR Associates, Inc
Doing interesting things with little computers since 1979.
More information about the inn-workers
mailing list