error inputting api key into cointop.sh.
I say "installing $: cointop
FATA[0000] Near line 80 (last key parsed 'coinmarketcap.pro_api_key'): unexpected EOF"
I need to put back in the proper API key as i goofed up the system,
I have deleted cointop from brew and reran the cointop but unfortently
i get the error below:
FATA[0000] Near line 80 (last key parsed 'coinmarketcap.pro_api_key'): unexpected EOF``
<code>
cointop
FATA[0000] Near line 80 (last key parsed 'coinmarketcap.pro_api_key'): unexpected EOF
</code>
I just wanted a simple install script for this but i'm not smart
and wanted to say oops to cointop for this error/fix.
cointop author here; this might have been fixed in the latest release but if you encounter issues like this even after installing the latest version then you can reset the config with cointop --reset (make sure to backup relevant changes first)
Related
I have tried to install ceedling for Windows 11. But come across this error:
Failed to load C:/ProgramData/gemrc, (<unknown>): control characters are not allowed at line 1 column 1
I installed Ruby 3.1.3.1 (x64) from here https://rubyinstaller.org/downloads/
Then I ran:
gem install ceedling
Any ideas on how to install ceedling correctly would be appreciated.
That error is telling you that the file C:\ProgramData\gemrc has invalid data in it at line 1, column 1. You have most likely edited this file improperly when installing Ruby because this is a default file with a default configuration that should have been created when you installed Ruby.
You should try these steps in order:
Inspect the file to see what invalid characters exist at that position, comparing it to some default gemrc files, and remove any invalid characters, or:
Rename the file and try again, or:
Remove the file and reinstall Ruby from scratch so that the file is created from scratch
I installed mssql using
npm install -g sql-cli
and it was installed succesfully.
The output after insallation:
`npm WARN deprecated sprintf#0.1.5: The sprintf package is deprecated in favor of sprintf-js.
npm WARN deprecated core-js#1.2.7: core-js#<3.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Please, upgrade your dependencies to the actual version of core-js.
/usr/local/Cellar/heroku-node/12.21.0/bin/mssql -> /usr/local/Cellar/heroku-node/12.21.0/lib/node_modules/sql-cli/bin/mssql
sql-cli#0.6.2
updated 1 package in 6.057s`
However, when I try to run
mssql -u sa -p myPassw0rd
I get an error that says
command not found: mssql on macOS
I also made sure that
/usr/local/Cellar/heroku-node/12.21.0/lib/node_modules/sql-cli/bin/mssql is in my $PATH variable
What is the solution to this issue?
I am using
npm v6.14.10
node v12.21.0
macOS Bug Sur 11.6
When adding sql-cli your path, make sure to add the directory containing the executable rather than the executable itself.
In your case, add /usr/local/Cellar/heroku-node/12.21.0/lib/node_modules/sql-cli/bin to your path, rather than /usr/local/Cellar/heroku-node/12.21.0/lib/node_modules/sql-cli/bin/mssql.
I've got the same error and I've seen some tutorials in youtube getting the same message. Changing the path did not work for me. I checked the logs docker logs <container_id> and got the message:
ERROR: Unable to set system administrator password: Password
validation failed. The password does not meet SQL Server password
policy requirements because it is not complex enough. The password
must be at least 8 characters long and contain characters from three
of the following four sets: Uppercase letters, Lowercase letters, Base
10 digits, and Symbols
When I used a different password, it started to work correctly despite of the warnings.
I'm having trouble reinstalling ProFTPD on a FreeBSD 10.1 setup. The server is newly upgraded from 10.0 to 10.1. When I start the make install clean process, these warnings first shows on screen.
===> proftpd-1.3.5_4 depends on shared library: libpcre.so
/usr/share/misc/magic, 93: Warning: Printf format `l' is not valid for type `lelong' in description `, %ld pages'
...
/usr/share/misc/magic, 15118: Warning: Printf format `l' is not valid for type `belong' in description `Volume %ld,'
/usr/share/misc/magic, 15609: Warning: Current entry does not yet have a description for adding a MIME type
file: File 5.19 supports only version 12 magic files. `/usr/share/misc/magic.mgc' is version 8
[: =: unexpected operator
- not found
And after i while, the make process stops with this error:
/bin/ln -s libpcre.so.1 /usr/ports/devel/pcre/work/stage/usr/local/lib/libpcre.so.3
====> Compressing man pages (compress-man)
===> Installing for pcre-8.35_2
===> Checking if pcre already installed
===> pcre-8.35_2 is already installed
You may wish to ``make deinstall'' and install this port again
by ``make reinstall'' to upgrade it properly.
If you really wish to overwrite the old port of pcre
without deleting it first, set the variable "FORCE_PKG_REGISTER"
in your environment or the "make install" command line.
*** Error code 1
Stop.
make[3]: stopped in /usr/ports/devel/pcre
*** Error code 1
Stop.
make[2]: stopped in /usr/ports/devel/pcre
*** Error code 1
Stop.
make[1]: stopped in /usr/ports/ftp/proftpd
*** Error code 1
Stop.
make: stopped in /usr/ports/ftp/proftpd
Seems that the file /usr/share/misc/magic.mgc is of a wrong version?
This might happens when I was upgrading from 10.0-RELEASE-p12 to 10.1-RELESE-p1?
If i run make install clean of the ProFTP port, and disable support for pcre, the process and install is successful.
But I believe that something is still broken?
My programming skills are limited, and also this level of error.
Please let me know if you have any ideas,
Thanks,
First of all, proftpd 1.3.5 is available as a binary package, it's much simpler to install it that way (pkg install proftpd).
Second - at first it looked like a port bug; as Etan said, there is a shell syntax error (something like '[ x == y ]' instead of '[ x = y ]'); those are common, and ports contain patches to fix those. However, there is a binary package, and packages are built from ports ("make package"), so port obviously does work on package build machines. So it's probably something specific to your environment.
If you really want to build from ports, try this: first, reinstall pcre. For some reason it had to be rebuilt, but failed to install, because it's already installed. So, "cd /usr/ports/*/pcre && make clean all deinstall reinstall". That should get rid of the second error. Then go back to "../*/proftpd" and see how far it goes.
But really, I'd try packages first. They have nothing in common with old pkg_add system, and are really nice.
freebsd-update diff for FreeBSD-SA-14:28.file seems wrong, and it breaks file(1).
Therefore simply pkg install file will be a workaround.
when i did sudo make install in the installation process of freeradius server,
i stucked about this error .
installing man1/CA.pl.1
installing man1/asn1parse.1
installing man1/ca.1
installing man1/ciphers.1
installing man1/cms.1
cms.pod around line 457: Expected text after =item, not a number
cms.pod around line 461: Expected text after =item, not a number
cms.pod around line 465: Expected text after =item, not a number
cms.pod around line 470: Expected text after =item, not a number
cms.pod around line 474: Expected text after =item, not a number
POD document had syntax errors at /usr/bin/pod2man line 71.
make: *** [install_docs] Error 255
if anyone else had aware about this,its now time to give remedies to solve this problem
That is not an error generated by the FreeRADIUS installation scripts. pod2man is not called by any of the build scripts, and there is no 'install_docs' target.
This seems not to come from building the Freeradius server itself but seems a common issue with (older?) OpenSSL releases. See e.g. this FreeBSD forum posting or these DuckDuckGo search results.
Additionally it's unclear why pod2man rejects valid POD syntax.
Update: It seems that pod2man doesn't dislike numbers in general, but dislikes one specific number: Zero. So try to change all cases of =item 0. to =item 1. and bump potential further =item <some number> by adding 1, too. Worked fine for me for fixing the same issue in the POD of Net::IRC.
When trying to upgrade MAMP pear the following error is raised:
Notice: unserialize(): Error at offset 276 of 1133 bytes in Config.php on line 1050
ERROR: The default config file is not a valid config file or is corrupted.
Some suggestions how to fix this?
Steps to reproduce:
Installed MAMP (version 2.0.5)
cd /Applications/MAMP/bin/php/php5.3.6/bin
sudo ./pear upgrade pear
above mentioned error is thrown
Update (1):
Based on answer 8375349/420953 I tried 2 possibilities to fix this
A: delete pear.conf
rm /Applications/MAMP/bin/php/php5.3.6/conf/pear.conf
B: edit pear.conf
change "php_dir";s:44 to "php_dir";s:43
both resulted in error:
Could not get contents of package "/Applications/MAMP/bin/php/php5.3.6/bin/pear". Invalid tgz file.
upgrade failed
Update (2):
running
which pear
results in output
/usr/local/bin/pear
With this, I noticed that I was using the "local" version of PEAR.
I removed it with
sudo pear uninstall pear
and then tried to upgrade the MAMP version of PEAR with
/Applications/MAMP/bin/php/php5.3.6/bin/pear upgrade pear
this results in error
Cannot install, php_dir for channel "pear.php.net" is not writeable by the current user
upgrading with
sudo /Applications/MAMP/bin/php/php5.3.6/bin/pear upgrade pear
installs it locally (again).
running
which pear
outputs
/usr/local/bin/pear
this brings me back to the starting point of Update (2). Seems that I am not able to upgrade PEAR under a MAMP directory.
Update (3):
I posted question
MAMP PEAR configuration is pointing to local directories
because my assumption is that the root of this issue is related to MAMP PEAR config.
Update (4):
I did not install a local PEAR version and this was causing quite some issues. After also installing a local version (and not only the MAMP) version, upgarding the MAMP version worked perfectly.
People with the your exact problem seem to has solved it in this MAMP forum thread.
You can either delete /Applications/MAMP/bin/php/php5.3.6/conf/pear.conf, or change a line in that file from "php_dir";s:44 to "php_dir";s:43.
Edit the pear.conf: Adding a forward slash "/" to the end of the php_dir path, while keeping the s:44 solved the problem for me and a couple coworkers.
I have XAMPP installed, and I just deleted /xampp/php/pear.ini and that solved the same problem
Just chipping in with a late response for others finding this answer. My PEAR config had several issues and not just the php_dir config setting.
I had to go over all of my settings to verify that the count was correct. When all errors where fixed my PEAR was working fine again.
Seeing this message in the terminal:
Notice: unserialize(): Error at offset 276 of 1133 bytes in Config.php on line 1050
ERROR: The default config file is not a valid config file or is corrupted.
Go to your PEAR Config file (probably located here /MAMP/bin/php/php7.0.10/conf/pear.conf)
Go to the 276th character in that file and verify that the string length matches the s43 that's defined before the string.
Run a PEAR command again (e.g. pear version)
If you have more errors located at e.g. 317th character you count that string and write the length in the s:XX before the string.
Just for clarifying for others finding this issue. The PEAR Config file is a serialized object that is unserialized when running commands.
A serialized object looks like s:5:"value" with the s:5 defining the length the string.