Welcome
Login  Sign up

Installation Error - Proxy Configuration Daemon not Running.

Hey guys, 


Ever since I upgraded to version 2.0 I am getting the following error... Installation Error  Proxy Configuration Daemon not Running..  Please reinstall Jaksta Recorder..


I have reinstalled the product over and over again. 


Thank you for your help. 


JS



Hi Alan,


Are you running any kind of cleaning/auto-delete program, specifically a program called Clean My Mac 3 (or anything similar)?


We have seen this program cause this problem in the past as it detects and deletes the proxy config daemon file, thinking that it is an unnecessary file for whatever reason. 


Also, do you have the app installed and running from the top level of the Applications folder? If not, that has been known to cause this issue as well.


One other thing that might help is updating your Mac OS, if you are happy to.


Regards

Liam

Jaksta Support

hi, no clean my mac or the like in it. I use appZapper for uninstalls. But ive been using it for 5years with no previous problemsCan you seed a screen shot of proxy setting and ill do it manually. when i search for that file its not there. what is the location of it?

"Are you running any kind of cleaning/auto-delete program, specifically a program called Clean My Mac 3 (or anything similar)?"


Yes, I'm running Clean My Mac 3.


Can you please copy the proxy config daemon file location on Mac so I can try to whitelist it?


Also, does missing proxy config daemon file really cause the endless spinning "beachball" as soon as Jaksta is run? Shouldn't it just report an error?

Hi Alan and T,


The location of the proxy config daemon file is: System/Library/LaunchDaemons/com.ProxyConfigDaemon.plist


'System' is the hard drive that your machine runs from. In my case that is Macintosh HD. 


Do not go looking for the file in your user profile file directory. You will not find it.


If you do have trouble finding it then I would suggest using the 'Go to Folder' option in Finder > Go, and then just put in the file path as: /Library/LaunchDaemons/


The file itself is com.ProxyConfigDaemon.plist and that is what you will want to whitelist/exclude from any cleaning or exclusion protocols you may have running.


From what we have seen, Clean My Mac 3 often causes problems even when it shouldn't. We have had users before who have reported that even after setting it to ignore the PCD file, it either still deletes it or it continues to interfere with Jaksta for unknown reasons. If this looks to be the case for you T, then I would suggest removing the software. 


Normally a proxy config daemon error is displayed when it is either missing or corrupted, but sometimes depending on the system or other factors (such as other software that interferes) it just hangs instead and gives the ongoing beach ball.


Regards

Liam

Jaksta Support


Hi John,


There is a couple of things I'll get you to check:

1. Are you running Jaksta from the top level of your Applications folder?
2. Is your Download Location in the Preferences > Downloads set to a place that still exists and is accessible? - ie. NOT an external drive that is no longer connected


Start with those checks and then let me know.


Regards

Liam

Jaksta Support

ok, if found the file, but i have only a adblocker running. so what do i do?

Liam, 


Thanks for your possible solutions, in all accounts, everything is running local, I am running the application from the application folder. Any other solutions? Like I mentioned before, the previous version ran with no issues at all, it was until I upgraded to version 2 that I am having issues. Do you need anything else?  Can you help me get this resolved? 


Thank you. 

JS

I am having the same problem ono 1.5.1 and V2


I'm on version 2.0.2 now and this problem occurs almost every week.

Fresh install...runs ok for a while, then that damned "Proxy Configuration Daemon not running" again.

 

Well, it ran 7 days without a problem and today when opening the app, I got the same old "Proxy Configuration Daemon not running" error again. This has happened countless times over the last months now. Reinstalling fresh from the latest install available online...then it breaks in a week or two.
=======
LOG
=======

2017-09-19 15:14:45.447 Jaksta Media Recorder[10072:148889] Config Daemon crash files in /Library/Logs/DiagnosticReports:
2017-09-19 15:14:45.447 Jaksta Media Recorder[10072:148889] /Library/RMC/ProxyConfigDaemon missing
2017-09-19 15:14:45.447 Jaksta Media Recorder[10072:148889] ***Showing Alert title:config.daemon.error.title text:config.daemon.error.msg
2017-09-19 15:14:45.447 Jaksta Media Recorder[10072:148889] ConfigDaemonClient:Waiting For Commands
2017-09-19 15:14:45.450 Jaksta Media Recorder[10072:148703] JAK: ====================================================
2017-09-19 15:14:45.450 Jaksta Media Recorder[10072:148703] JAK: Task /usr/sbin/netstat
Routing tables

Internet:
Destination        Gateway            Flags        Refs      Use   Netif Expire
default            192.168.8.1        UGSc          577        0     en0
127                127.0.0.1          UCS             1        0     lo0
127.0.0.1          127.0.0.1          UH             19    33686     lo0
169.254            link#4             UCS             1        0     en0
192.168.8          link#4             UCS             2        0     en0
192.168.8.1/32     link#4             UCS             2        0     en0
192.168.8.1        58:7f:66:d0:8c:51  UHLWIir       578     1237     en0   1184
192.168.8.102/32   link#4             UCS             1        0     en0
192.168.8.255      link#4             UHLWbI          1       99     en0
224.0.0            link#4             UmCS            2        0     en0
224.0.0.251        1:0:5e:0:0:fb      UHmLWI          1        0     en0
255.255.255.255/32 link#4             UCS             1        0     en0

Internet6:
Destination                             Gateway                         Flags         Netif Expire
::1                                     ::1                             UHL             lo0
fe80::%lo0/64                           fe80::1%lo0                     UcI             lo0
fe80::1%lo0                             link#1                          UHLI            lo0
fe80::%en0/64                           link#4                          UCI             en0
fe80::6e40:8ff:fe97:d684%en0            6c:40:8:97:d6:84                UHLI            lo0
fe80::%awdl0/64                         link#9                          UCI           awdl0
fe80::3440:7eff:fec5:bc0a%awdl0         36:40:7e:c5:bc:a                UHLI            lo0
ff01::%lo0/32                           ::1                             UmCI            lo0
ff01::%en0/32                           link#4                          UmCI            en0
ff01::%awdl0/32                         link#9                          UmCI          awdl0
ff02::%lo0/32                           ::1                             UmCI            lo0
ff02::%en0/32                           link#4                          UmCI            en0
ff02::%awdl0/32                         link#9                          UmCI          awdl0
2017-09-19 15:14:45.450 Jaksta Media Recorder[10072:148703] JAK: ====================================================
2017-09-19 15:14:47.377 Jaksta Media Recorder[10072:148703] JAK: Checking Activation State
2017-09-19 15:14:47.377 Jaksta Media Recorder[10072:148703] JAK: Checked, Starting - Activated = yes
2017-09-19 15:14:48.304 Jaksta Media Recorder[10072:148703] Connection finished
2017-09-19 15:14:57.377 Jaksta Media Recorder[10072:148703] ***** Activated
2017-09-19 15:14:57.377 Jaksta Media Recorder[10072:148703] ***** Check on Startup
2017-09-19 15:14:57.377 Jaksta Media Recorder[10072:148703] ShedUpdate checking for updates
2017-09-19 15:14:57.378 Jaksta Media Recorder[10072:148703]
::ShedUpdate::
:: checking url: http://www.jaksta.com/Services/VersionDirector/jmr-mac?v=2.0.2
2017-09-19 15:14:57.378 Jaksta Media Recorder[10072:148703]
::ShedUpdate::
:: checking version: 2.0.2
2017-09-19 15:14:58.530 Jaksta Media Recorder[10072:148703]
::ShedUpdate::
:: finsh check
2017-09-19 15:14:58.530 Jaksta Media Recorder[10072:148703]
::ShedUpdate::
:: No update
2017-09-19 15:15:35.587 Jaksta Media Recorder[10072:148703] ContentBO.getFolder: Fetched OK. Got 0 rows.
2017-09-19 15:15:35.587 Jaksta Media Recorder[10072:148703] tableController:: REload
2017-09-19 15:15:36.210 Jaksta Media Recorder[10072:148703] ContentBO.getFolder: Fetched OK. Got 0 rows.
2017-09-19 15:15:36.210 Jaksta Media Recorder[10072:148703] tableController:: REload
2017-09-19 15:15:36.661 Jaksta Media Recorder[10072:148703] ContentBO.getFolder: Fetched OK. Got 0 rows.
2017-09-19 15:15:36.661 Jaksta Media Recorder[10072:148703] tableController:: REload
2017-09-19 15:15:37.953 Jaksta Media Recorder[10072:148703] At doChangeMonitoring!
2017-09-19 15:15:37.953 Jaksta Media Recorder[10072:148703] Wait For Cert Auth Key - Start
2017-09-19 15:15:37.953 Jaksta Media Recorder[10072:148889] Unable To Connect To ConfigDaemon on path /var/run/ProxyConfigDaemon, msg:No such file or directory
2017-09-19 15:15:37.953 Jaksta Media Recorder[10072:148889] Unable To Connect To ConfigDaemon - May not be installed correctly
2017-09-19 15:15:37.953 Jaksta Media Recorder[10072:148889] ***Showing Alert title:config.daemon.error.title text:config.daemon.error.msg
2017-09-19 15:15:37.953 Jaksta Media Recorder[10072:148703] Wait For Cert Auth Key - End
2017-09-19 15:15:37.953 Jaksta Media Recorder[10072:148889] ConfigDaemonClient:Waiting For Commands
2017-09-19 15:15:37.953 Jaksta Media Recorder[10072:148703] Cert Auth Read Config keybytes:0, certbytes:0
2017-09-19 15:16:27.960 Jaksta Media Recorder[10072:148703] JAK: PreferencesController.init
2017-09-19 15:16:27.987 Jaksta Media Recorder[10072:148703] JAK: PreferencesController.awakeFromNib
2017-09-19 15:17:37.870 Jaksta Media Recorder[10072:148703] JAK: Preferences changed
2017-09-19 15:17:53.388 Jaksta Media Recorder[10072:148703] JAK: windowWillClose
2017-09-19 15:18:00.223 Jaksta Media Recorder[10072:148703] At doChangeMonitoring!
2017-09-19 15:18:00.223 Jaksta Media Recorder[10072:148703] Wait For Cert Auth Key - Start
2017-09-19 15:18:00.223 Jaksta Media Recorder[10072:148889] Unable To Connect To ConfigDaemon on path /var/run/ProxyConfigDaemon, msg:No such file or directory
2017-09-19 15:18:00.223 Jaksta Media Recorder[10072:148889] Unable To Connect To ConfigDaemon - May not be installed correctly
2017-09-19 15:18:00.223 Jaksta Media Recorder[10072:148889] ***Showing Alert title:config.daemon.error.title text:config.daemon.error.msg
2017-09-19 15:18:00.223 Jaksta Media Recorder[10072:148703] Wait For Cert Auth Key - End
2017-09-19 15:18:00.223 Jaksta Media Recorder[10072:148703] Cert Auth Read Config keybytes:0, certbytes:0
2017-09-19 15:18:00.223 Jaksta Media Recorder[10072:148889] ConfigDaemonClient:Waiting For Commands
2017-09-19 15:18:32.244 Jaksta Media Recorder[10072:148703] JAK: windowWillClose
2017-09-19 15:19:10.015 Jaksta Media Recorder[10072:148703] At doChangeMonitoring!
2017-09-19 15:19:10.015 Jaksta Media Recorder[10072:148703] Wait For Cert Auth Key - Start
2017-09-19 15:19:10.015 Jaksta Media Recorder[10072:148889] Unable To Connect To ConfigDaemon on path /var/run/ProxyConfigDaemon, msg:No such file or directory
2017-09-19 15:19:10.015 Jaksta Media Recorder[10072:148889] Unable To Connect To ConfigDaemon - May not be installed correctly
2017-09-19 15:19:10.015 Jaksta Media Recorder[10072:148889] ***Showing Alert title:config.daemon.error.title text:config.daemon.error.msg
2017-09-19 15:19:10.015 Jaksta Media Recorder[10072:148703] Wait For Cert Auth Key - End
2017-09-19 15:19:10.015 Jaksta Media Recorder[10072:148889] ConfigDaemonClient:Waiting For Commands
2017-09-19 15:19:10.015 Jaksta Media Recorder[10072:148703] Cert Auth Read Config keybytes:0, certbytes:0
2017-09-19 15:19:12.654 Jaksta Media Recorder[10072:148703] ContentBO.getFolder: Fetched OK. Got 0 rows.
2017-09-19 15:19:12.654 Jaksta Media Recorder[10072:148703] tableController:: REload
2017-09-19 15:19:13.644 Jaksta Media Recorder[10072:148703] ContentBO.getFolder: Fetched OK. Got 0 rows.
2017-09-19 15:19:13.644 Jaksta Media Recorder[10072:148703] tableController:: REload
2017-09-19 15:19:14.090 Jaksta Media Recorder[10072:148703] ContentBO.getFolder: Fetched OK. Got 0 rows.
2017-09-19 15:19:14.090 Jaksta Media Recorder[10072:148703] tableController:: REload

 

Hi T,


Can you please try running it again and then when it crashes open Console and go to var/log/ProxycongigDaemon.log, and send through the ProxycongigDaemon.log file.


Regards

Liam

Jaksta Support

Hi Alan,


The log is showing that crash reports are being generated as a result of the PCD error. So it would be helpful if we could get those. 


You can find them by opening the Console app and then use the side menu to navigate to /Library/Logs/Diagnostic Reports/ and there should be something in there that stands out. Might look something like ProxyConfigDaemon.crash


If you don't see anything there then try looking in ~/Library/Logs/Diagnostic Reports/ (the paths look similar but one has the '~' at the start of the file path). There may be a file that looks something like Jaksta Media Recorder________________.crash, where the blank space has the date it was generated and an ID number. This may be the only crash file that you find. Regardless of what else you find, send through the one dated as the most recent. 


Also, if you look in /var/log there should be a file called ProxyConfigDaemon.log. Send that as well as it contains additional PCD information. 


Regards

Liam

Jaksta Support

Hi John,


The next best thing to do would be to send through a clean copy of the log file. From what we should hopefully be able to see when the problem starts and what causes it.


To get a clean log, you will need to do the following.

- Open JMR

- Go to Preferences > General > Find Log File

- Close JRM but keep the Finder window with the log file open

- Delete the log file and still keep the Finder window open

- Reopen JMR (this will generate a new log file)

- Run JMR until you get the error

- Close JMR

- Go back to the Finder window the new log file and grab that log file and attach it here (don't copy and paste the code in it - send the file itself)


At any point does the program actually crash at all? Or do you just get that message and then it stays open? If it crashes, then you might also be able to get a copy of the crash log. To get it, when you reopen JMR you should get a notice saying 'JMR has crashed etc.' and it will give you three options - Reopen, Report, Ignore. If you click on 'Report' then it should take you to another screen where you can press another button to get the crash log. If you get that far, then same thing again and just attach the file here so I can take a look.


Regards

Liam

Jaksta Support

Liam, 


Thanks for your support. Please, help me resolve this issue, I am very frustrated with the product, it worked fine for almost a year, then after the update it quit working.. as per your request, here is the log file. 


Let me know what else I can do.. 



log

Liam, 


To answer the last part of your question, the program will not crash, it remains open but is not functional after that. 


Thanks 

JS


Login or Signup to post a comment