Hi. A mongrel/rails installation (proxyed through apache) is crashing for some reason with the following error found in the mongrel.log: ERROR: meta.c (179): wmf_header_read: this isn''t a wmf file /root/local/radiant/config/../vendor/rails/activerecord/lib/active_record/base.rb:2068: [BUG] Segmentation fault ruby 1.8.4 (2005-12-24) [i386-linux] Fedora 5 mongrel: 0.3.13.3 Apache/2.2.0 Any ideads? TIA. --M
On 8/1/06, Maurizio Balestrieri <maurizio at gmail.com> wrote:> Hi. A mongrel/rails installation (proxyed through apache) is crashing > for some reason with the following error found in the mongrel.log: > > ERROR: meta.c (179): wmf_header_read: this isn''t a wmf file > /root/local/radiant/config/../vendor/rails/activerecord/lib/active_record/base.rb:2068: > [BUG] Segmentation fault > ruby 1.8.4 (2005-12-24) [i386-linux] > > Fedora 5 > mongrel: 0.3.13.3 > Apache/2.2.0 > > Any ideads? TIA.If ruby is crashing it''s probably a bug in the C extension it''s using. Check where that meta.c is from. Seems to be something for video files? WMF? Pedro.
On 8/1/06, Josh Ferguson <josh at besquared.net> wrote:> They are with radiant, and most likely with caching on RHEL/FC with the > apache 2.2/mongrel 0.3.13 combo. Are you running this radiant on a > virtual server or a machine that is all your own?Josh, It''s a VPS on rimuhosting with 256MB RAM, and the same system software stack you mentioned (including radiant).
Maurizio I''m fighting with the same problems on a production machine. They are with radiant, and most likely with caching on RHEL/FC with the apache 2.2/mongrel 0.3.13 combo. Are you running this radiant on a virtual server or a machine that is all your own? Josh Maurizio Balestrieri wrote:> Hi. A mongrel/rails installation (proxyed through apache) is crashing > for some reason with the following error found in the mongrel.log: > > ERROR: meta.c (179): wmf_header_read: this isn''t a wmf file > /root/local/radiant/config/../vendor/rails/activerecord/lib/active_record/base.rb:2068: > [BUG] Segmentation fault > ruby 1.8.4 (2005-12-24) [i386-linux] > > Fedora 5 > mongrel: 0.3.13.3 > Apache/2.2.0 > > Any ideads? TIA. > > --M > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > >
Maurizio I''m fighting with similar problems with radiant on a production machine where mongrel segfaults for various reasons at different times. It seems random to me so my guess it that the problem is with caching on RHEL/FC with the apache 2.2/mongrel 0.3.13 combo which is what I''m running. Are you running this radiant on a virtual server or a machine that is all your own? Josh Maurizio Balestrieri wrote:> Hi. A mongrel/rails installation (proxyed through apache) is crashing > for some reason with the following error found in the mongrel.log: > > ERROR: meta.c (179): wmf_header_read: this isn''t a wmf file > /root/local/radiant/config/../vendor/rails/activerecord/lib/active_record/base.rb:2068: > [BUG] Segmentation fault > ruby 1.8.4 (2005-12-24) [i386-linux] > > Fedora 5 > mongrel: 0.3.13.3 > Apache/2.2.0 > > Any ideads? TIA. > > --M > _______________________________________________ > Mongrel-users mailing list > Mongrel-users at rubyforge.org > http://rubyforge.org/mailman/listinfo/mongrel-users > >
On Tue, 2006-08-01 at 11:30 +0200, Maurizio Balestrieri wrote:> Hi. A mongrel/rails installation (proxyed through apache) is crashing > for some reason with the following error found in the mongrel.log: > > ERROR: meta.c (179): wmf_header_read: this isn''t a wmf file > /root/local/radiant/config/../vendor/rails/activerecord/lib/active_record/base.rb:2068: > [BUG] Segmentation fault > ruby 1.8.4 (2005-12-24) [i386-linux] >Did you solve this Maurizio? Did you see a similar posting earlier about RMagick and missing LD_* configurations when run under sudo? -- Zed A. Shaw http://www.zedshaw.com/ http://mongrel.rubyforge.org/ http://www.railsmachine.com/ -- Need Mongrel support?
On 8/3/06, Zed Shaw <zedshaw at zedshaw.com> wrote:> Did you solve this Maurizio? Did you see a similar posting earlier > about RMagick and missing LD_* configurations when run under sudo?Hello Zed. This issue happened in the past roughly every couple of days, based on rather moderate usage pattern of a radiant powered site. At the end of the day, I tended to link it with radiant and its cache handling mechanism when the page content is a large CSS file ... I don''t know exactly why I started linking all this factors and I don''t have a proof of their relevance in causing the accident though. What I did was installing the latest mongrel (the one still in beta) suggested as a possible remedy for segfault, and using a CSS file (stored in the file system rather than in a radiant page--by sqlite3). So far the problem has not shown up again. I''ll let you know if it happens again. Thank you. --M