Not sure if this was an issue prior to beta 5 as I have only just noticed it…
The repo backup dir is creating the “most recent” backup OK, but the date/time stamp dir is created “2013-09-23_14-34-15”, but it is empty!
Hmm, all of our date/time folders have stuff in there. Maybe this was a one off case where it failed. If you check the temp folder on your system, there should be bitrock installer logs there. If you can post one from the session where this happened, we can take a look.
Thanks!
Ah ok…so, repo installer was executed on OSX.
I have no logs in /tmp or /var/log, I assume + 1 x google search later, indicates it should be stored in /tmp when on OSX platform…but nothing…
So, as I installed it yesterday and have restarted since, has it been purged? There is a variable in the Bitrock installer build which allows developers to auto-delete the installer log after install. Have you guys got this enabled?
No, we don’t have that option enabled. I checked my OSX machine, and I still have a log in /tmp. If it’s been purged on your machine, I’m not actually sure what would cause that…
Strange…
So, I have run the repo installer 3 more times this morning…
bitrock_installer.log is indeed created in /tmp during install, together with the temp repo directory, full of files, etc.
tail -f bitrock_installer.log during install looks all ok:
[code]Log started 09/25/2013 at 11:18:22
Preferred installation mode : osx
Trying to init installer in mode osx
Mode osx successfully initialized
Executing uname -m
Script exit code: 0
Script output:
x86_64
Script stderr:
This can take a few minutes
This can take a few minutes
Configuring database (this may take a few minutes)
Executing /tmp/repoinstalltemp/mono/Mono.framework/Versions/2.10.9/bin/mono “/tmp/repoinstalltemp/deadlinecommand.exe” -ConfigureDatabase “MongoDB” “mbp.local” “deadlinedb” “27017” “0” “false” “0” “” “”
Script exit code: 0
Script output:
Database successfully configured!
Database Type: MongoDB
Hostname(s): mbp.local
Database Name: deadlinedb
Port: 27017
Alt. Port: 0
SSL Enabled: False
Authenticate: False
User Name:
Password:
Script stderr:
Preparing to Install
Backing up repository
Backing up repository
Backing up binaries
Backing up events
Backing up plugins
Backing up scripts
Backing up submission scripts
Preparing to Install
Unpacking files
Updating database settings
Executing /tmp/repoinstalltemp/mono/Mono.framework/Versions/2.10.9/bin/mono “/tmp/repoinstalltemp/deadlinecommand.exe” -UpdateDatabaseSettings “/Applications/Thinkbox/DeadlineRepository6” “MongoDB” “mbp.local” “deadlinedb” “27017” “0” “false” “0” “” “”
Script exit code: 0
Script output:
Script stderr:
Updating plugin and event settings
Executing /tmp/repoinstalltemp/mono/Mono.framework/Versions/2.10.9/bin/mono “/tmp/repoinstalltemp/deadlinecommand.exe” -UpgradePluginSettings “/Applications/Thinkbox/DeadlineRepository6”
Script exit code: 0
Script output:
Script stderr:
Removing temporary files
Creating Uninstaller
Creating uninstaller 25%
Creating uninstaller 50%
Creating uninstaller 75%
Creating uninstaller 100%
Installation completed
Log finished 09/25/2013 at 11:23:41[/code]
Now comes the fun. /tmp always gets purged 100% on reboot of my OSX v10.8.5 machine! I haven’t set anything on a scheduled task to do this and multiple google searches don’t flag up any change in OSX 10.8 nor a launchd embedded plist agent/daemon that is doing this upon reboot. However, it’s happening and I have no idea why!
A quick “stat” on the log file shows that it’s atime/ctime/mtime are all correct and today’s date (OSX will cleanup any files more than 3 days old out of /tmp) - [this is the default setting in OSX it would seem]
Anyway, back to the real issue…so, it all seems to be backing up now with both a “mostRecent” and a “timestamp” directory. BUT, I think there might be an issue when it comes to the scripts/custom directory backup…
Am I right when I say; “the timestamp directory is a copy of the “mostRecent” directory and time stamps it with the date at THAT time of running the installer?” So, I think the issue is that the VERY FIRST time you run the installer with ZERO backups, the “mostRecent” directory gets populated and a “timeStamp” directory gets created but is EMPTY as the above operation doesn’t take place. ie: You need to run the installer AT LEAST 2 times, before you will get a “timeStamp” directory populated with files/directories?
Hopefully, the above makes sense and maybe it’s just my misunderstanding of how it works? What happens to the log file when you reboot your OSX machine? Is it on 10.8.5?
Thanks,
Mike
Hey Mike,
I checked our repository installer logic, and we only create the timestamp folder if a mostRecent folder already exists, at which point the contents are copied from the mostRecent folder to the timestamp folder. So the very first time you run it, you should only have a mostRecent folder in the backup folder.
I just happened to restart my Mac this morning, and sure enough the /tmp folder had been purged. Must be a “feature”. 
Cheers,
- Ryan
Understood. I’ll double-check it on the next beta release. Thanks