6 years agoDoug Whitfield created SDP-423 for slight typo in comment /p4/INSTANCe/checkpoints Line 9 at https://swarm.workshop.perforce.com/files/guest/perforce_software/sdp/dev/Server/Unix/p4/co...mmon/bin/recreate_offline_db.sh has a lowercase 'e' in INSTANCE, when the rest of the word is caps. I'm not sure if the caps are the typo or if the 'e' is the typo. « | ||
Add a comment | ||
6 years agoDoug Whitfield commented on change 23823 (jiratest.php, line 25) for Not sure how all of this is going to be formatted in the comments, but will post this here until we can get an official patch. The below will allow th ...Not sure how all of this is going to be formatted in the comments, but will post this here until we can get an official patch. The below will allow the test to work using Zend 3: --- jiratest.orig.php 2019-08-19 20:23:48.384156147 +0000 // setup autoloading
| ||
6 years agoDoug Whitfield commented on change 23823 (jiratest.php, line 6) for All of the Zend stuff has been moved. This one to /opt/perforce/swarm/vendor/zendframework/zend-http/src/Client ...not sure at present how the "use" s ...All of the Zend stuff has been moved. This one to /opt/perforce/swarm/vendor/zendframework/zend-http/src/Client ...not sure at present how the "use" syntax maps to the filesystem syntax as used below « | ||
6 years agoDoug Whitfield commented on change 23823 (jiratest.php, line 18) for this path is not valid in Swarm 2019.1. Is /opt/perforce/swarm/vendor/zendframework/zend-loader/src/AutoloaderFactory.php | ||
6 years agoDoug Whitfield created job000745 for perforce_software-admin-toolkit: Nvidia would like to be able to pass arguments to p4dstate.sh much like the SDP version of p4dstate.sh. However, they do not have an SDP. Their need... for this is driven by having multiple p4d instances on the same device. Thus, using environment variables, and hard-coding paths in multiple versions of the script would both require work on their side. The request is about the following lines in the script: p4d=/<absolute-path-to->/p4d p4=/<absolute-path-to->/p4 P4ROOT=/<absolute-path-to-P4ROOT> P4LOG=/<absolute-path-to->/log P4JOURNAL=/<absolute-path-to->/journal P4PORT=<p4d-listener> P4USER=<perforce-superuser> « | ||
6 years agoDoug Whitfield created SDP-381 for Windows recover doc does not give correct path The doc gives this path: c:\p4\instance\bin\p4_1 This is what is actually looks like: C:\sdp\Serve...r\Windows\setup>ls C:\p4\2\bin\ daily-backup.bat p4.exe p4d.exe p4s.exe p4verify.bat replica-status.bat C:\sdp\Server\Windows\setup>ls C:\p4\1\bin\ daily-backup.bat p4.exe p4d.exe p4s.exe p4verify.bat replica-status.bat I also assume that last bit should be p4_instance rather than p4_1, but I am not sure of that « | ||
6 years agoDoug Whitfield created SDP-376 for Windows guide instructions are confusing when paired with script output The output of Create_env.py -y tells you: Please run the following commands:... install_services_10.104.1.153.bat configure_Master.bat You will also need to seed the replicas from a checkpoint and run the appropriate commands on those machines However, you can't run those until you've setup the service. The guide isn't really wrong, but it's confusing. Page 11-12 of https://swarm.workshop.perforce.com/view/guest/perforce_software/sdp/dev/doc/SDP_Guide_Windows.pdf « | ||
6 years agoDoug Whitfield commented on SDP-364 for that perforce/r17.1 also goes nowhere. Would be nice to use ftp://ftp.perforce.com/perforce/r18.2/bin.ntx64/p4.exe and then we could just iterate the ...that perforce/r17.1 also goes nowhere. Would be nice to use ftp://ftp.perforce.com/perforce/r18.2/bin.ntx64/p4.exe and then we could just iterate the version # as needed « | ||
6 years agoDoug Whitfield created SDP-373 for Typo on page 22 of guide (Section 4.2): modifed vs modified | ||
6 years agoDoug Whitfield created SDP-364 for Improvements in Windows PDF I. Version #s don't match: "a. The desired release of Windows of p4.exe and p4d.exe, e.g. for release 15.1 and 64... bit Windows: http://perforce/r17.1/bin.ntx64/p4d.exe http://perforce/r17.1/bin.ntx64/p4.exe " II. Not sure if typo or we support a version of python where they no longer release Windows binaries. Either way, not a good user experience: "Download and install Python, e.g. from www.python.org. We use Python 2.7.x (latest) and 3.4.x (latest). " « | ||
6 years agoDoug Whitfield created SDP-360 for | ||
7 years agoDoug Whitfield created SDP-349 for Make it more clear when P4Python fails The end of the SDP install script says: SUCCESS: SDP Configuration complete. If by dumb luck you n...otice P4Python failed you can go to the log and find the following: zipimport.ZipImportError: can't decompress data; zlib not available I don't know that bailing is the appropriate action, but I don't think SUCCESS without a caveat is really correct either. It makes me wonder what else might have failed that I didn't see. « | ||
7 years agoDoug Whitfield modified PSLA-3 for perforce-software-log-analyzer: Docker instructions flawed Looking at https://swarm.workshop.perforce.com/files/guest/perforce_software/utils/log_analyzer/README.md the docker instr...uctions appear to be flawed (perhaps a newer version of Docker is required?) perforce@dwhitfield-ubuntu2012vsphere:~$ make build docker build -t psla psla docker - version 1.4 Copyright 2003, Ben Jansens <ben@orodu.net> Usage: docker [OPTIONS] Options: -help Show this help. -display DISPLAY The X display to connect to. -border The width of the border to put around the system tray icons. Defaults to 1. -vertical Line up the icons vertically. Defaults to horizontally. -wmaker WindowMaker mode. This makes docker a fixed size (64x64) to appear nicely in in WindowMaker. Note: In this mode, you have a fixed number of icons that docker can hold. -iconsize SIZE The size (width and height) to display icons as in the system tray. Defaults to 24. -color COLOR The background color to use for the tray. Defaults to whatever color the window manager specifies. make: *** [build] Error 1 « | ||
7 years agoDoug Whitfield commented on job000736 for Looks like the appropriate link is probably https://www.perforce.com/perforce/doc.current/manuals/p4api/index.html | ||
7 years agoDoug Whitfield created job000736 for perforce_software-p4: www.perforce.com/perforce/technical.html no longer exists. https://swarm.workshop.perforce.com/projects/perforce_software-p4/files/2018-1/api/p4api.cc... references this URL. I'm not sure the correct place at the moment. I will attempt to find and place in the comments. « | ||
7 years agoDoug Whitfield commented on PSLA-3 for Still though: perforce@dwhitfield-despair:~$ make build Still though: perforce@dwhitfield-despair:~$ make build | ||
7 years agoDoug Whitfield commented on PSLA-3 for It would seem this is not the docker you are looking for... docker - System tray for KDE3/GNOME2 docklet applications package is actually docker.io. | ||
7 years agoDoug Whitfield created PSLA-3 for perforce-software-log-analyzer: Looking at https://swarm.workshop.perforce.com/files/guest/perforce_software/utils/log_analyzer/README.md the docker instructions appear to be flawed... (perhaps a newer version of Docker is required?) perforce@dwhitfield-ubuntu2012vsphere:~$ make build docker build -t psla psla docker - version 1.4 Copyright 2003, Ben Jansens <ben@orodu.net> Usage: docker [OPTIONS] Options: -help Show this help. -display DISPLAY The X display to connect to. -border The width of the border to put around the system tray icons. Defaults to 1. -vertical Line up the icons vertically. Defaults to horizontally. -wmaker WindowMaker mode. This makes docker a fixed size (64x64) to appear nicely in in WindowMaker. Note: In this mode, you have a fixed number of icons that docker can hold. -iconsize SIZE The size (width and height) to display icons as in the system tray. Defaults to 24. -color COLOR The background color to use for the tray. Defaults to whatever color the window manager specifies. make: *** [build] Error 1 « | ||
7 years agoDoug Whitfield created job000734 for perforce-software-p4php: link in "About" is broken. | ||
7 years agoDoug Whitfield commented on job000730 for "OpenNMS's NRPE support is...not used or maintained, and may not be reliable." So... | ||
7 years agoDoug Whitfield created job000732 for perforce_software-p4nagios: examine efficiency of license check | ||
7 years agoDoug Whitfield created job000730 for perforce_software-p4nagios: Native OpenNMS support. Current support is through NRPE. This may require a fork and a separate project, but it might not. It may also be that NRPE co...uld still be used, but the output could be improved for OpenNMS. Ultimately, this is early days, as we have not begun testing on OpenNMS. Please feel free to add jobs for additional monitoring tools, and we can look into it. « | ||
7 years agoDoug Whitfield modified job000724 for perforce_software-p4nagios: Add HTH functionality | ||
7 years agoDoug Whitfield modified job000728 for perforce_software-p4nagios: Helix4Git checks (please add separately if you still think we need Git Fusion) | ||
7 years agoDoug Whitfield modified job000723 for perforce_software-p4nagios: Add Swarm Functionality | ||
7 years agoDoug Whitfield created job000729 for perforce_software-p4nagios: Make Wizard (this would be for XI) | ||
7 years agoDoug Whitfield committed change 24103 into now with license | ||
7 years agoDoug Whitfield commented on change 24102 (restful.sh) for This is supposed to be part of P4Nagios, but I messed it up. This is GPL...which will get added here in a second | ||
7 years agoDoug Whitfield committed change 24102 into adding api check | ||
7 years agoDoug Whitfield created job000728 for perforce_software-p4nagios: Helix4Git checks (please add separately if you still think we need Git Fusion) | ||
7 years agoDoug Whitfield created job000727 for perforce_software-p4nagios: warn on long running commands. | ||
7 years agoDoug Whitfield created job000726 for perforce_software-p4nagios: check btree depths. | ||
7 years agoDoug Whitfield created job000725 for perforce_software-p4nagios: highlight when replication slows down. | ||
7 years agoDoug Whitfield commented on job000723 for This was on the roadmap listed at https://swarm.workshop.perforce.com/projects/perforce_software-p4nagios/ | ||
7 years agoDoug Whitfield commented on job000723 for We could just pull in check_http as a start. One of my former colleagues also created an API check, which I could probably get from him. | ||
7 years agoDoug Whitfield created job000724 for perforce_software-p4nagios: Add HTH functionality | ||
7 years agoDoug Whitfield created job000723 for perforce_software-p4nagios: Add Swarm Functionality | ||
7 years agoDoug Whitfield created HI-5 for perforce_software-helix-installer: Automatically delete (or rename) reset_sdp.sh "After the initial install, the reset_sdp.sh script should be removed." I read the above and though...t...why don't we just delete it? Well, the initial answer is obvious: they may still be testing. Forcing the users to redownload the reset_sdp.sh seems better than overwriting their production system them. I suspect this falls under not being able to keep a root user from shooting themselves in the foot, but I think it's worth thinking about. I'd suggest auto delete after 90 days, possibly 60. One option that would keep someone from accidentally running a command in their history would be to change the name of the script after each run. Then you have reset_sdp.sh1 to "infinity". This is slightly irritating if you are testing, but adding a digit to your command doesn't seem too hard. It might be fun to see how many times you've reset things anyway. It may be that this is beneficial, but not worth the implementation effort. It's just thought. If there was a "super low" severity option, I'd pick that. :) « | ||
7 years agoDoug Whitfield committed change 23860 into douglasawh-p4nagios:main "Forking branch Main of perforce_software-p4nagios to douglasawh-p4nagios." | ||
Adjust when notifications are sent to you about reviews that you're associated with (as an author, reviewer, project member or moderator).