Not one response so far on install problem

[slas7713]

I'm trying to quell my disappointment with the OScommerce and general support but it's difficult. I'm more surprised that I've NOT received one single response to any problem I've posted on this problamatic install. Maybe I'm on the wrong forum for support. If I am please let me know where I might go to get some much needed answers.

 

I'm still stuck at at this error when trying to access the Administration Tool or Catalog (from httpd-error.log):

[notice] child pid xxx exit signal Segmentation fault (11)

 

I'm curious if anyone who has installed the register_globals patch has had a similar problem. I'm thinking it's possibly something in the files that were implemented in the patch but I'm just guessing and hoping that someone, anyone, can give me insight. The other suggestions for the register_globals would not work, I promise I tried them all that were listed here and on the web.

 

I've researched this new error all day today (three days total trying to install only) and some have suggested hardware memory issues and such but I have PHP working on all my other sites without issue. I've uninstalled and reinstalled php4, mysql, and oscommerce twice now. I don't believe this is a hardware or OS problem since I haven't had any other related problems besides this one. I will wait to see if I can get any answers and if not I will scrap the OScommerce implementation until it becomes more implementation friendly, or less buggy, and pay for a stable solution for my clients.

 

Dean L

[moonstone]

I'm trying to quell my disappointment with the OScommerce and general support but  it's difficult. I'm more surprised that I've NOT received one single response to any problem I've posted on this problamatic install. Maybe I'm on the wrong forum for support. If I am please let me know where I might go to get some much needed answers.

 

I'm still stuck at at this error when trying to access the Administration Tool or Catalog (from httpd-error.log):

[notice] child pid xxx exit signal Segmentation fault (11)

 

I'm curious if anyone who has installed the register_globals patch has had a similar problem. I'm thinking it's possibly something in the files that were implemented in the patch but I'm just guessing and hoping that someone, anyone, can give me insight. The other suggestions for the register_globals would not work, I promise I tried them all that were listed here and on the web.

 

I've researched this new error all day today (three days total trying to install only) and some have suggested hardware memory issues and such but I have PHP working on all my other sites without issue. I've uninstalled and reinstalled php4, mysql, and oscommerce twice now. I don't believe this is a hardware or OS problem since I haven't had any other related problems besides this one. I will wait to see if I can get any answers and if not I will scrap the OScommerce implementation until it becomes more implementation friendly, or less buggy, and pay for a stable solution for my clients.

 

Dean L

<{POST_SNAPBACK}>

 

 

I can understand your frustration in not getting any assistance.

 

However, let's be fair to the osCommerce team. osCommerce 2.2 MS2 is indeed a quality release and certainly implementation friendly. I have not experienced any major bugs since I started using it around 3 years ago.

 

"Register Globals Patch" is a contribution (use at your own risk). And contributions are not all written by the osCommerce team. In fact, most contributions are written by fellow users and shared with the community. As such, we cannot expect the team to support even codes which they have no part in writing. If you have read the news, you would have known that a number of team members have left some time ago, and the current team is already short handed in the development of MS3.

 

If you refer to the workboard, you will see that "register_globals compatibility" is still work in progress for 2.2-MS3. As such, if you insistently want to enable register_globals, you can either rely solely on the patch which is a contribution, or wait for the release of MS3. If the installation of the patch caused any errors, it will either be a problem with the contribution or problems in the way the contribution is installed.

 

I'll suggest you try to have the register_globals disabled for the time being, and wait for the release of MS3. Anyway, that's the intended environment for MS2 when it was being developed. Frankly, I had been running my store in that setting for the past few years, and everything's well. :blush:

[♥Vger]

The problem you've posted is not an osCommerce fault. You would have done better to do a search on Google for the error message you are getting. Google is full of posts on this subject, and this is just one of them (relates to hardware fault, or trying to access memory you're not allowed to access):

 

http://lists.debian.org/debian-apache/2002/07/msg00005.html

 

As for Register Globals, yes apply the patch by all means but it does make quite clear that Register Globals has to be set to 'off' in php.ini if you use the patch.

 

Vger

[slas7713]

Vger,

 

I decided to go one more day before finally giving up. The mention of hardware issues in my post above is in relations to the URL you've pointed out. I made it through 14 pages of google based on my search "Segmentation fault (11)". It seems the php code is trying to access memory it is not allowed to. It's the where, why and how that's the question. Serveral realate to PHP and PERL issues also. I've turned on my mirror so I can work solely on the server in question today. I'm going to rebuild the kernel and all start from the ground up on loading all dependencies for OScommerce.

 

Moonstone:

I have found one bug reported for OScommerce on this exact issue but there was only the bug report that was tagged "unassigned" and no other information related to it so it is possible that this is a oscommerce related issue since there's at least one other out there with the exact same problem.

 

We'll see how the last day goes and in no way do I mean to be disrespectful of the developers who give their time freely to make this all happen. I'm an open source fan who is just frustrated with this install.

 

Dean L

 

The problem you've posted is not an osCommerce fault.  You would have done better to do a search on Google for the error message you are getting.  Google is full of posts on this subject, and this is just one of them (relates to hardware fault, or trying to access memory you're not allowed to access):

 

http://lists.debian.org/debian-apache/2002/07/msg00005.html

 

As for Register Globals, yes apply the patch by all means but it does make quite clear that Register Globals has to be set to 'off' in php.ini if you use the patch.

 

Vger

<{POST_SNAPBACK}>