Re: [Mono-dev] xbuild - ** ERROR **: shm_semaphores_init: semget error: No space left on device.
On Fri, 2010-11-12 at 13:11 -0800, Arne Claassen wrote: > Right, that's why I'm confused. That release states "Users seeking > absolute stability should stay on Mono 2.6", but my impression is that > all bug fixes are just going into 2.8. "Stability" generally means "minimal changes." The bug fixes going into 2.8 likely change lots of code, and thus have had (comparatively) little testing, whereas the aim of 2.6 is to fix bugs while making as few changes as possible (as we don't want a fix for one bug to introduce another). - Jon ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] xbuild - ** ERROR **: shm_semaphores_init: semget error: No space left on device.
Right, that's why I'm confused. That release states "Users seeking absolute stability should stay on Mono 2.6", but my impression is that all bug fixes are just going into 2.8. cheers, Arne Claassen MindTouch San Diego, CA http://twitter.com/sdether On Nov 12, 2010, at 10:48 AM, Oskar Berggren wrote: > The release notes have some info > http://www.mono-project.com/Release_Notes_Mono_2.8 > > /Oskar > > > 2010/11/12 Arne Claassen : >> Sounds like i just need to build 2.8, since more and more things i >> run >> into seem to be taken care of in 2.8. >> >> This is going off-topic, but it's something that I haven't gotten a >> handle on yet with mono release process: >> >> Is 2.8 the new stable or still in flux? If it's stable, when might >> there be rpms or at least an RPM spec. >> >> Basically, I don't want to build from source for every server i set >> up >> and I want to make sure every server runs identical code. This is why >> I've been sticking with 2.6.x, assuming it's still the stable and >> fixes would still trickle into it. Is that not correct? >> >> If I can help with building or testing RPMs and their specs for 2.8, >> let me know, I know that there's always tons to do and too few people >> available to do it. >> >> thanks, >> Arne Claassen >> >> MindTouch >> San Diego, CA >> http://twitter.com/sdether >> >> On Nov 12, 2010, at 10:10 AM, Robert Jordan wrote: >> >>> On 12.11.2010 19:06, Arne Claassen wrote: I can try that. But more importantly, I'd like to learn more about about semaphore usage. >>> >>> Their usage has been faded out in 2.8. >>> I'm just wildly speculating, but i assume it sets up a new one for IPC when an application gets compiled into a new appdomain by ASP.NET when it detects code changes. But shouldn't those semaphores get released when the old appdomain gets unloaded? Is this a sign of appdomains not being unloaded or just not cleaning up their semaphores? And shouldn't they all get released regardless when the mod_mono processes gets shut down? Would love to get more insight into what's happening, but don't really know where to start. >>> >>> Have a look at mono/io-layer/, but, as I wrote, they are not >>> enabled by default anymore. >>> >>> Robert >>> >>> ___ >>> Mono-devel-list mailing list >>> Mono-devel-list@lists.ximian.com >>> http://lists.ximian.com/mailman/listinfo/mono-devel-list >> >> ___ >> Mono-devel-list mailing list >> Mono-devel-list@lists.ximian.com >> http://lists.ximian.com/mailman/listinfo/mono-devel-list >> ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] xbuild - ** ERROR **: shm_semaphores_init: semget error: No space left on device.
The release notes have some info http://www.mono-project.com/Release_Notes_Mono_2.8 /Oskar 2010/11/12 Arne Claassen : > Sounds like i just need to build 2.8, since more and more things i run > into seem to be taken care of in 2.8. > > This is going off-topic, but it's something that I haven't gotten a > handle on yet with mono release process: > > Is 2.8 the new stable or still in flux? If it's stable, when might > there be rpms or at least an RPM spec. > > Basically, I don't want to build from source for every server i set up > and I want to make sure every server runs identical code. This is why > I've been sticking with 2.6.x, assuming it's still the stable and > fixes would still trickle into it. Is that not correct? > > If I can help with building or testing RPMs and their specs for 2.8, > let me know, I know that there's always tons to do and too few people > available to do it. > > thanks, > Arne Claassen > > MindTouch > San Diego, CA > http://twitter.com/sdether > > On Nov 12, 2010, at 10:10 AM, Robert Jordan wrote: > >> On 12.11.2010 19:06, Arne Claassen wrote: >>> I can try that. But more importantly, I'd like to learn more about >>> about semaphore usage. >> >> Their usage has been faded out in 2.8. >> >>> >>> I'm just wildly speculating, but i assume it sets up a new one for >>> IPC >>> when an application gets compiled into a new appdomain by ASP.NET >>> when >>> it detects code changes. But shouldn't those semaphores get released >>> when the old appdomain gets unloaded? Is this a sign of appdomains >>> not >>> being unloaded or just not cleaning up their semaphores? And >>> shouldn't >>> they all get released regardless when the mod_mono processes gets >>> shut >>> down? >>> >>> Would love to get more insight into what's happening, but don't >>> really >>> know where to start. >> >> Have a look at mono/io-layer/, but, as I wrote, they are not >> enabled by default anymore. >> >> Robert >> >> ___ >> Mono-devel-list mailing list >> Mono-devel-list@lists.ximian.com >> http://lists.ximian.com/mailman/listinfo/mono-devel-list > > ___ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list > ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] xbuild - ** ERROR **: shm_semaphores_init: semget error: No space left on device.
Sounds like i just need to build 2.8, since more and more things i run into seem to be taken care of in 2.8. This is going off-topic, but it's something that I haven't gotten a handle on yet with mono release process: Is 2.8 the new stable or still in flux? If it's stable, when might there be rpms or at least an RPM spec. Basically, I don't want to build from source for every server i set up and I want to make sure every server runs identical code. This is why I've been sticking with 2.6.x, assuming it's still the stable and fixes would still trickle into it. Is that not correct? If I can help with building or testing RPMs and their specs for 2.8, let me know, I know that there's always tons to do and too few people available to do it. thanks, Arne Claassen MindTouch San Diego, CA http://twitter.com/sdether On Nov 12, 2010, at 10:10 AM, Robert Jordan wrote: > On 12.11.2010 19:06, Arne Claassen wrote: >> I can try that. But more importantly, I'd like to learn more about >> about semaphore usage. > > Their usage has been faded out in 2.8. > >> >> I'm just wildly speculating, but i assume it sets up a new one for >> IPC >> when an application gets compiled into a new appdomain by ASP.NET >> when >> it detects code changes. But shouldn't those semaphores get released >> when the old appdomain gets unloaded? Is this a sign of appdomains >> not >> being unloaded or just not cleaning up their semaphores? And >> shouldn't >> they all get released regardless when the mod_mono processes gets >> shut >> down? >> >> Would love to get more insight into what's happening, but don't >> really >> know where to start. > > Have a look at mono/io-layer/, but, as I wrote, they are not > enabled by default anymore. > > Robert > > ___ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] xbuild - ** ERROR **: shm_semaphores_init: semget error: No space left on device.
On 12.11.2010 19:06, Arne Claassen wrote: > I can try that. But more importantly, I'd like to learn more about > about semaphore usage. Their usage has been faded out in 2.8. > > I'm just wildly speculating, but i assume it sets up a new one for IPC > when an application gets compiled into a new appdomain by ASP.NET when > it detects code changes. But shouldn't those semaphores get released > when the old appdomain gets unloaded? Is this a sign of appdomains not > being unloaded or just not cleaning up their semaphores? And shouldn't > they all get released regardless when the mod_mono processes gets shut > down? > > Would love to get more insight into what's happening, but don't really > know where to start. Have a look at mono/io-layer/, but, as I wrote, they are not enabled by default anymore. Robert ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] xbuild - ** ERROR **: shm_semaphores_init: semget error: No space left on device.
I can try that. But more importantly, I'd like to learn more about about semaphore usage. I'm just wildly speculating, but i assume it sets up a new one for IPC when an application gets compiled into a new appdomain by ASP.NET when it detects code changes. But shouldn't those semaphores get released when the old appdomain gets unloaded? Is this a sign of appdomains not being unloaded or just not cleaning up their semaphores? And shouldn't they all get released regardless when the mod_mono processes gets shut down? Would love to get more insight into what's happening, but don't really know where to start. thanks, Arne Claassen MindTouch San Diego, CA http://twitter.com/sdether On Nov 12, 2010, at 4:02 AM, Rafael Teixeira wrote: > Have you tried to set MONO_DISABLE_SHM? From the top of my mind there > is where a huge use of semaphores are used to simulate the shared > memory files used for cross-process, but I may be mixing things. If > you're using it you can try to disable it, and see if things gets > better. > > Just my two cents, > Rafael "Monoman" Teixeira > --- > "We live in a world operated by science and technology. We have also > arranged things so that almost no one understands science and > technology. This is a prescription for disaster. We might get away > with it for a while, but sooner or later this combustible mixture of > ignorance and power is going to blow up in our faces." > -Carl Sagan > > > On Fri, Nov 12, 2010 at 4:53 AM, Arne Claassen > wrote: >> >> I'm running mono 2.6.7 (novell rpms) on centos 5.5 w/ mod_mono and >> I've twice run into xbuild stopping to work with this error: >> >> ** ERROR **: shm_semaphores_init: semget error: No space left on >> device. >> >> I don't have the full error right now, since i rebooted the machine >> again and didn't capture it first. But it talks about either removing >> semaphores using ipcrm and ipcs or increasing the max semaphores >> >> After restart, ipcs has no Semaphore Arrays, but after i hit my >> various asp.net apps, that output quickly goes up: >> >> >> -- Shared Memory Segments >> keyshmid owner perms bytes nattch >> status >> 0x0101400b 327680 root 60052828 45 >> 0x01014069 360449 root 60052828 26 >> 0x740102df 131074 root 6004 0 >> 0x010140af 393219 root 60052828 26 >> 0x010140b1 425988 root 60052828 26 >> >> -- Semaphore Arrays >> keysemid owner perms nsems >> 0x 0 root 6001 >> 0x 65537 apache 6001 >> 0x 98306 apache 6001 >> 0x 131075 apache 6001 >> 0x 163844 apache 6001 >> 0x 196613 apache 6001 >> >> etc. >> >> When the error occured, that list of arrays was about 100 long. >> restarting apache, mod_mono, etc didn't help. Killing off semaphores >> using ipcrm seemed to get xbuild working again, but the asp.net apps >> then only returned blank pages. Finally I rebooted again. >> >> Not knowing what those semaphores are and what makes them increase, >> leaves me a bit worried. Do i just need more semphores (and how do i >> do that) or is xbuild just creating them and never cleaning them up? >> Any help understanding what this means and how to either prevent or >> at >> least clean it up would be greatly appreciated. >> >> cheers, >> Arne Claassen >> >> MindTouch >> San Diego, CA >> http://twitter.com/sdether >> >> ___ >> Mono-devel-list mailing list >> Mono-devel-list@lists.ximian.com >> http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
Re: [Mono-dev] xbuild - ** ERROR **: shm_semaphores_init: semget error: No space left on device.
Have you tried to set MONO_DISABLE_SHM? From the top of my mind there is where a huge use of semaphores are used to simulate the shared memory files used for cross-process, but I may be mixing things. If you're using it you can try to disable it, and see if things gets better. Just my two cents, Rafael "Monoman" Teixeira --- "We live in a world operated by science and technology. We have also arranged things so that almost no one understands science and technology. This is a prescription for disaster. We might get away with it for a while, but sooner or later this combustible mixture of ignorance and power is going to blow up in our faces." -Carl Sagan On Fri, Nov 12, 2010 at 4:53 AM, Arne Claassen wrote: > > I'm running mono 2.6.7 (novell rpms) on centos 5.5 w/ mod_mono and > I've twice run into xbuild stopping to work with this error: > > ** ERROR **: shm_semaphores_init: semget error: No space left on device. > > I don't have the full error right now, since i rebooted the machine > again and didn't capture it first. But it talks about either removing > semaphores using ipcrm and ipcs or increasing the max semaphores > > After restart, ipcs has no Semaphore Arrays, but after i hit my > various asp.net apps, that output quickly goes up: > > > -- Shared Memory Segments > key shmid owner perms bytes nattch status > 0x0101400b 327680 root 600 52828 45 > 0x01014069 360449 root 600 52828 26 > 0x740102df 131074 root 600 4 0 > 0x010140af 393219 root 600 52828 26 > 0x010140b1 425988 root 600 52828 26 > > -- Semaphore Arrays > key semid owner perms nsems > 0x 0 root 600 1 > 0x 65537 apache 600 1 > 0x 98306 apache 600 1 > 0x 131075 apache 600 1 > 0x 163844 apache 600 1 > 0x 196613 apache 600 1 > > etc. > > When the error occured, that list of arrays was about 100 long. > restarting apache, mod_mono, etc didn't help. Killing off semaphores > using ipcrm seemed to get xbuild working again, but the asp.net apps > then only returned blank pages. Finally I rebooted again. > > Not knowing what those semaphores are and what makes them increase, > leaves me a bit worried. Do i just need more semphores (and how do i > do that) or is xbuild just creating them and never cleaning them up? > Any help understanding what this means and how to either prevent or at > least clean it up would be greatly appreciated. > > cheers, > Arne Claassen > > MindTouch > San Diego, CA > http://twitter.com/sdether > > ___ > Mono-devel-list mailing list > Mono-devel-list@lists.ximian.com > http://lists.ximian.com/mailman/listinfo/mono-devel-list ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
[Mono-dev] xbuild - ** ERROR **: shm_semaphores_init: semget error: No space left on device.
I'm running mono 2.6.7 (novell rpms) on centos 5.5 w/ mod_mono and I've twice run into xbuild stopping to work with this error: ** ERROR **: shm_semaphores_init: semget error: No space left on device. I don't have the full error right now, since i rebooted the machine again and didn't capture it first. But it talks about either removing semaphores using ipcrm and ipcs or increasing the max semaphores After restart, ipcs has no Semaphore Arrays, but after i hit my various asp.net apps, that output quickly goes up: -- Shared Memory Segments keyshmid owner perms bytes nattch status 0x0101400b 327680 root 60052828 45 0x01014069 360449 root 60052828 26 0x740102df 131074 root 6004 0 0x010140af 393219 root 60052828 26 0x010140b1 425988 root 60052828 26 -- Semaphore Arrays keysemid owner perms nsems 0x 0 root 6001 0x 65537 apache 6001 0x 98306 apache 6001 0x 131075 apache 6001 0x 163844 apache 6001 0x 196613 apache 6001 etc. When the error occured, that list of arrays was about 100 long. restarting apache, mod_mono, etc didn't help. Killing off semaphores using ipcrm seemed to get xbuild working again, but the asp.net apps then only returned blank pages. Finally I rebooted again. Not knowing what those semaphores are and what makes them increase, leaves me a bit worried. Do i just need more semphores (and how do i do that) or is xbuild just creating them and never cleaning them up? Any help understanding what this means and how to either prevent or at least clean it up would be greatly appreciated. cheers, Arne Claassen MindTouch San Diego, CA http://twitter.com/sdether ___ Mono-devel-list mailing list Mono-devel-list@lists.ximian.com http://lists.ximian.com/mailman/listinfo/mono-devel-list
