Closed Bug 227518 Opened 21 years ago Closed 20 years ago

syncshadowdb fails because the cat command is not found

Categories

(Bugzilla :: Administration, task)

2.16
Sun
SunOS
task
Not set
major

Tracking

()

RESOLVED WONTFIX

People

(Reporter: charlotte.allen, Assigned: justdave)

Details

(Whiteboard: [does not affect trunk])

User-Agent: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0 Build Identifier: Mozilla/5.0 (X11; U; SunOS sun4u; en-US; rv:1.0.1) Gecko/20020920 Netscape/7.0 On creation of shadowdb, the syncshadowdb script fails because the 'cat' command is not in the path of sh Reproducible: Always Steps to Reproduce: 1. Set up shadowdb 2. Run 'syncshadowdb -syncall' from the command line Actual Results: get this output: Acquiring lock Syncing up the shadow database by copying entire database in. Disabled reading from the shadowdb. Sleeping 10 seconds to let other procs catch up. Locking entire database Dumping database to a temp file (data/tmpsyncshadow.21211). Restoring from tempfile into shadowdb sh: cat: not found Reenabling other processes to read from the shadow db OK, done. Looking for commands to execute. Releasing lock. Expected Results: Acquiring lock Syncing up the shadow database by copying entire database in. Disabled reading from the shadowdb. Sleeping 10 seconds to let other procs catch up. Locking entire database Dumping database to a temp file (data/tmpsyncshadow.21217). Restoring from tempfile into shadowdb ...................................................................... ...................................................................... ...................................................................... ...................................................................... ..................................................................... Reenabling other processes to read from the shadow db OK, done. Looking for commands to execute. Releasing lock.
Hmm. So you mean cat isn't in /usr/bin, or do you have a very short PATH?
Actually, we outright nuke the path because of taint problems. That should have never worked and I have no idea why it did on bmo when we were using it there. That's the reason we record the path to the mysql binaries from checksetup.pl and pass it a full path when shelling out to mysqldump. The shadow database feature of Bugzilla (as far as Bugzilla itself maintaining the shadow) is deprecated and no longer supported. We recommend using MySQL's built-in replication as it's much more accurate and less error prone. If you're on an installation which is having enough performance problems to require using a shadow database you should really be running 2.17.4 or later because there are other significant performance improvements as well. That said, if someone comes up with a low-risk patch to fix this, I'll take it on the 2.16 branch.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Whiteboard: [does not affect trunk]
Target Milestone: --- → Bugzilla 2.16
Obviously nobody has had enough interest in this to create a patch, as there have been no comments in over a year. And the shadowdb is deprecated. I don't see this bug ever being fixed. I'd imagine that symlinking /usr/bin/cat to your actual "cat" should work.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → WONTFIX
Version: unspecified → 2.16
clearing target of DUPLICATE/WONTFIX/INVALID/WORKSFORME so they'll show up as untriaged if they get reopened.
Target Milestone: Bugzilla 2.16 → ---
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.