A. What ibays are missing, and is there anything unusual about them?What do you get from
db accounts show |grep '=ibay'Specifically, does the listing include the missing ibays, and if so, what are the names of those ibays?
Is there anything odd looking about the access rights to those ibays (
ls -l /home/e-smith/files/ibays)?
B. Name conflicts with users or groups?The
ibay chapter in the admin manual includes this note (emphasis added):
Note:
When you create an i-bay, the name may be up to 12 characters long #4 and may contain only lower-case letters, numbers, periods and underscores. The i-bay name should also start with a lower-case letter. For example, johnson, sales and client3.prj8 are all valid names, while 3associates, John Smith and Bus-Partner are not. Finally, an i-bay cannot use the same name as an existing user or group account. It must be unique. Note that there are two special names, primary and public, which are in use by the system and cannot be used for an i-bay name.
If the missing ibays are included in the output from the first command (above) you can check for duplicate account names using this one-liner:
db accounts show |grep '=ibay' |sed 's/=ibay//' |while read ibay; do grep "$ibay" /home/e-smith/db/accounts; done|grep -v '=ibay'Explanation:
* get the ibays from db accounts (then remove '=ibay')
* iterate through the ibay names, searching for every row in the accounts database containing the ibay name
* remove the actual '=ibay' rows from the results
There should be no output. If there is any output your system has non-ibay accounts that duplicate ibay names.
C. signal-event post-upgrade; signal-event rebootThere's a chance that simply running
signal-event post-upgrade; signal-event reboot might find and fix whatever problem you're running into.
Or - the resulting messages in
/var/log/messages may tell you where to look.
8 Replies
1891 Views