trading
/
PTMagic
mirror of https://github.com/PTMagicians/PTMagic.git
2
0
Fork 0
Code Issues Releases Wiki Activity

Updated Common Errors (markdown)

HojouFotytu 2021-04-19 11:45:05 +09:00
parent bb6f0c57cc
commit ce0b043ba4
1 changed files with 18 additions and 18 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

36
Common-Errors.md

@ -1,61 +1,61 @@
### OMG I forgot my password! ## OMG I forgot my password!
Relax! Just delete the file "settings.secure.json" in your "PTMagic" folder. You will be asked to create a new password as soon as you call the monitor website again. Relax! Just delete the file "settings.secure.json" in your "PTMagic" folder. You will be asked to create a new password as soon as you call the monitor website again.
### PT Magic or Monitor refuses to start (without errors) ## PT Magic or Monitor refuses to start (without errors)
If you right click the CMD file and choose properties, then you should see something like “this has been downloaded from another computer and is blocked. Please unblock ...” Click the unblock box and apply. If you right click the CMD file and choose properties, then you should see something like “this has been downloaded from another computer and is blocked. Please unblock ...” Click the unblock box and apply.
### Error when starting monitor ## Error when starting monitor
After you have finished the installation of **PT Magic**, started the application, then the monitor application (webserver) and browse to http://localhost:5000 the brwoser shows this error message: After you have finished the installation of **PT Magic**, started the application, then the monitor application (webserver) and browse to http://localhost:5000 the brwoser shows this error message:
> Could not find a part of the path '/home/user/ptmagic/ptmagic/_data/LastRuntimeSummary.json' > Could not find a part of the path '/home/user/ptmagic/ptmagic/_data/LastRuntimeSummary.json'
This may be caused by the fact that the **PT Magic** application did not finish its first run yet. This can take up to 10-15 minutes because it collects a lot of data from the exchange for the last 24 hours to build the market trends. The summary file as well as the _data folder is created after that has been completed. This may be caused by the fact that the **PT Magic** application did not finish its first run yet. This can take up to 10-15 minutes because it collects a lot of data from the exchange for the last 24 hours to build the market trends. The summary file as well as the _data folder is created after that has been completed.
### FATAL - Error loading configuration! ## FATAL - Error loading configuration!
If you setup the **Profit Trailer** path in "settings.general.json" and "Monitor/appsettings.json", make sure you use DOUBLE backslashes in the path. Otherwise you get the follwing error: If you setup the **Profit Trailer** path in "settings.general.json" and "Monitor/appsettings.json", make sure you use DOUBLE backslashes in the path. Otherwise you get the follwing error:
`FATAL - Error loading configuration! System.FormatException Could not parse the JSON file` `FATAL - Error loading configuration! System.FormatException Could not parse the JSON file`
### Loading Properties failed for setting SETTINGNAME ## Loading Properties failed for setting SETTINGNAME
This means you have specified a settings file in one of your global settings, but PTM cannot find it. Remember, the properties files must be in a folder with the EXACT same name as the global setting, and you MUST at least have one global setting named DEFAULT. See [this wiki entry for more details].(https://github.com/PTMagicians/PTMagic/wiki/Writing-Properties#1-using-a-preset-file) This means you have specified a settings file in one of your global settings, but PTM cannot find it. Remember, the properties files must be in a folder with the EXACT same name as the global setting, and you MUST at least have one global setting named DEFAULT. See [this wiki entry for more details].(https://github.com/PTMagicians/PTMagic/wiki/Writing-Properties#1-using-a-preset-file)
### FATAL - Error loading configuration! Newtonsoft.Json.JsonSerializationException Unexpected end when deserializing object. Path 'GeneralSettings', line X, position X ## FATAL - Error loading configuration! Newtonsoft.Json.JsonSerializationException Unexpected end when deserializing object. Path 'GeneralSettings', line X, position X
You are missing a closing bracket at the end of the previous object in your settings. You are missing a closing bracket at the end of the previous object in your settings.
### (Profit Trailer) ERROR AppErrorController - Invalid api_token received - No data returned <br><br> (PT Magic) The remote server returned an error: (401) Unauthorized <br><br> (PT Magic) No Server API Token specified. ## (Profit Trailer) ERROR AppErrorController - Invalid api_token received - No data returned <br><br> (PT Magic) The remote server returned an error: (401) Unauthorized <br><br> (PT Magic) No Server API Token specified.
For PTM to access PT's API and get required data, you need to set an API token in your PT settings, and then add that token to your Profit Trailer settings.general.json file. See: (https://wiki.profittrailer.com/doku.php?id=web_interface_guide#server_settings) and (https://github.com/PTMagicians/PTMagic/releases/tag/2.1.0). For PTM to access PT's API and get required data, you need to set an API token in your PT settings, and then add that token to your Profit Trailer settings.general.json file. See: (https://wiki.profittrailer.com/doku.php?id=web_interface_guide#server_settings) and (https://github.com/PTMagicians/PTMagic/releases/tag/2.1.0).
### Unhandled Exception: System.NullReferenceException / Object Reference not set to an instance of an object. ## Unhandled Exception: System.NullReferenceException / Object Reference not set to an instance of an object.
Your settings.general.json file is unable to find a necessary setting in the "Application" section, either because it has been omitted, or a comma is missing at the end of the previous line. Check that you have a comma at the end of every line in your settings (except the last), check the example default settings that come with PTM, or check the release notes (and prior releases) for any REQUIRED settings changes that you might have skipped since you last updated PTMagic. Your settings.general.json file is unable to find a necessary setting in the "Application" section, either because it has been omitted, or a comma is missing at the end of the previous line. Check that you have a comma at the end of every line in your settings (except the last), check the example default settings that come with PTM, or check the release notes (and prior releases) for any REQUIRED settings changes that you might have skipped since you last updated PTMagic.
### PTMagic has been raiding since (DATE) (TIME). Checking things... / PTMagic raid is taking longer than expected ## PTMagic has been raiding since (DATE) (TIME). Checking things... / PTMagic raid is taking longer than expected
This usually happens when a raid takes longer than the **IntervalMinutes** you've set in settings.analzyer.json. The interval has elapsed, and PTM is trying to start a new raid, but the previous raid is still being executed. This not a serious problem, however, descreasing resource usage by other applications, or increasing PTM's priority can help speed up raids. If your analyzer is too complex (too many market trends, or global/SMS settings) or using very large time frames (multiple days) for market trends, this can also make the raids take significantly longer. This usually happens when a raid takes longer than the **IntervalMinutes** you've set in settings.analzyer.json. The interval has elapsed, and PTM is trying to start a new raid, but the previous raid is still being executed. This not a serious problem, however, descreasing resource usage by other applications, or increasing PTM's priority can help speed up raids. If your analyzer is too complex (too many market trends, or global/SMS settings) or using very large time frames (multiple days) for market trends, this can also make the raids take significantly longer.
### Unhandled Exception: Newtonsoft.Json.JsonReaderException ## Unhandled Exception: Newtonsoft.Json.JsonReaderException
Your settings.general.json file is likely missing a comma after one of your settings. You can also use a [JSON validator](https://codebeautify.org/jsonvalidator) tool to check for other errors. Your settings.general.json file is likely missing a comma after one of your settings. You can also use a [JSON validator](https://codebeautify.org/jsonvalidator) tool to check for other errors.
### Expected keyword (True, False, and, or) but found... ## Expected keyword (True, False, and, or) but found...
This means you are using a buy/sell FORMULA in your PT settings, but the logic of your formula is incorrect. Please ask on the PT discord to make sure your formula is correct. If it is, but you still get this error be sure you are using spaces between all your arguments: eg., "(A && B) || (A && C)" This means you are using a buy/sell FORMULA in your PT settings, but the logic of your formula is incorrect. Please ask on the PT discord to make sure your formula is correct. If it is, but you still get this error be sure you are using spaces between all your arguments: eg., "(A && B) || (A && C)"
### Expected/Missing parenthesis ## Expected/Missing parenthesis
See above See above
### Empty expression ## Empty expression
This can occur when you are using a buy/sell FORMULA in your PT settings and a negation symbol before one of the strategy labels. For example, (A && B && !C). For PTM to correctly parse this formula, the strategy with negation should be enclosed in parenthesis like this: (A && B && (!C)) This can occur when you are using a buy/sell FORMULA in your PT settings and a negation symbol before one of the strategy labels. For example, (A && B && !C). For PTM to correctly parse this formula, the strategy with negation should be enclosed in parenthesis like this: (A && B && (!C))
### Dashboard (top) update failed! ## Dashboard (top) update failed!
You can find more information about this error by using the url: http://localhost:8000/_get/DashboardTop (change the port to match your PTM port. You can find more information about this error by using the url: http://localhost:8000/_get/DashboardTop (change the port to match your PTM port.
### Ticker update failed! - PTMagic Monitor failed to update data. ## Ticker update failed! - PTMagic Monitor failed to update data.
This is often caused by an incorrect setting in settings.general.json This is often caused by an incorrect setting in settings.general.json
See: [settings.general.json](https://github.com/PTMagicians/PTMagic/wiki/settings.general#timezoneoffset) See: [settings.general.json](https://github.com/PTMagicians/PTMagic/wiki/settings.general#timezoneoffset)
### Missing DLL(s) on older windows versions ## Missing DLL(s) on older windows versions
If you start seeing something like this: If you start seeing something like this:
![](https://cdn.discordapp.com/attachments/414927200161366029/420936009581330432/unknown.png) ![](https://cdn.discordapp.com/attachments/414927200161366029/420936009581330432/unknown.png)
@ -63,7 +63,7 @@ If you start seeing something like this:
You may want to update your Universal C Runtime for Windows: You may want to update your Universal C Runtime for Windows:
https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows
### Debian/Unix - Segfault error ## Debian/Unix - Segfault error
Solution (thanks to @Arararararagi): Solution (thanks to @Arararararagi):
`sudo apt remove libssl1.0.0/now` `sudo apt remove libssl1.0.0/now`
@ -71,7 +71,7 @@ Solution (thanks to @Arararararagi):
`sudo apt-get upgrade` `sudo apt-get upgrade`
`sudo apt-get install libssl1.0.2` `sudo apt-get install libssl1.0.2`
### High CPU usage on Unix systems ## High CPU usage on Unix systems
Some users reported high CPU usage on Unix systems and at least for some users the issue was fixed but installing/updating the Curl/libcurl package on their machine like this: Some users reported high CPU usage on Unix systems and at least for some users the issue was fixed but installing/updating the Curl/libcurl package on their machine like this: