Magento 2 Installation - Key must not exceed 56 bytes - linux

I'm having issues installing Magento 2 via command line. When setup is running it gets to:
Module 'Magento_Indexer':
Running recurring..
And it throws an error:
[Magento\Framework\Exception\LocalizedException]
Key must not exceed 56 bytes.
I have searched around and couldn't find any clues as to what it can be. I thought the --key might be too long for Magento setup but I have tried the setup without --key, as it is optional but the error still occurs.
2016/07/08 14:42:49 [error] 30074#30074: *1 FastCGI sent in stderr: "PHP message: PHP Fatal error: Uncaught exception 'Magento\Framework\Exception\LocalizedException' with message 'Key must not exceed 56 bytes.' in /magento/lib/internal/Magento/Framework/Encryption/Crypt.php:58
Stack trace:
0 /magento/lib/internal/Magento/Framework/Encryption/Encryptor.php(401): Magento\Framework\Encryption\Crypt->__construct('oon5eeRee7yiemo...', 'blowfish', 'ecb', false)
1 /magento/lib/internal/Magento/Framework/Encryption/Encryptor.php(313): Magento\Framework\Encryption\Encryptor->getCrypt('oon5eeRee7yiemo...', 0, false)
2 /magento/app/code/Magento/Config/Model/Config/Backend/Encrypted.php(107): Magento\Framework\Encryption\Encryptor->decrypt('PayPal')
3 /magento/lib/internal/Magento/Framework/App/Config/MetadataProcessor.php(86): Magento\Config\Model\Config\Backend\Encrypted->processValue('PayPal')
4 /magento/lib/internal/Magento/Framework/App/Config/Data.php(32): Magento\Framework\App\Config\MetadataPr" while reading response header from upstream, client: 127.0.0.1, server: www.magentotest.com, request: "GET /setup/ HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "www.magentotest.com"
If anyone could help that would be great, thank you!

app/etc/env.php is populated with the details of your installation. Look at the contents crypt, and make sure that key doesn't have multiple lines appended to it, as was the case in my new installation, after running the setup:install multiple times.
Changing this key for a current install would obviously be a bad idea. If this fixes you out, please let me know so I can log a ticket.

Related

Python 3.8.5 FTPS connection

I'm trying to do a FTPS (or FTP) connection to a FTP server. This is done on Python 3.8.5 32 bit via Visual Studio Code.
Here is the code:
import ftplib
session = ftplib.FTP_TLS('server address')
#session.connect ('server address', 991)
session.login(user='username',passwd='password')
#session.prot_p()
session.set_pasv(True)
session.cwd("files")
print(session.pwd())
filename = "ftpTest.txt"
my_file = open('filepath\\ftpTest.txt', 'wb') # Open a local file to store the downloaded file
session.retrbinary('RETR ' + filename, my_file.write, 1024)
session.quit()
I am able to get the session.pwd (which display /files) but the connection timeout at line 11 (session.retrbinary) in approximately 22 sec with the following error:
Exception has occurred: TimeoutError
[WinError 10060] A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
I had tried setting session.set_pasv to both True and False following Python ftplib timing out. Setting it True raised the TimeoutError and setting it False raise the following error at line 11:
Exception has occurred: error_perm
500 Illegal PORT command
and also tried setting a different port (991) following Python SSL FTP connection timing out and it raised the Timeout Error at line 3.
Using FTP without TLS raised the following error at line 4 (session.login):
Exception has occurred: error_perm
530 Non-anonymous sessions must use encryption.
Turning off my McAfee LiveSafe firewall didnt help either.
Btw file transfer works with Filezilla, was able to freely transfer.
Setting up the secure data connection and changing the session af to INET6 seemed to work for me. This was suggested to me by a colleague, and as to why it works is beyond me. If anyone can provide a proper explanation, please do.
Code:
session.login(user='username',passwd='password')
session.prot_p()
session.af = socket.AF_INET6

Cachet: Dashboard login outputs 500 error

So, I'm trying to set this up since yesterday.
As one of the troubleshooting steps I tried to change the directory in cachet-installation/bootstrap/autoload.php to the full path of the directory. After I knew that it doesn’t work I changed it back, but it just doesn’t wanna apply. I tried clearing the cache folder, but still nothing. This is copied from the nginx log: PHP message: PHP Fatal error: require(): Failed opening required '/home/cachet/www/bootstrap/home/cachet/www/vendor/autoload.php' (include_path='.:/usr/share/php') in /home/cachet/www/bootstrap/autoload.php on line 28" while reading response header from upstream, client: x.x.x.x, server: status.sqlstatement.de, request: "GET /setup HTTP/1.1", upstream: "fastcgi://unix:/var/run/php-fpm-cachet.sock:", host: "status.sqlstatement.de", referrer: "https://status.sqlstatement.de/setup".
I hope somebody here can help me.
I just reinstalled the server and it worked.

Chef-server-ctl reconfigure/ Creating Admin User on chef server

I am fairly new to Linux (and brand new to chef) and I have ran into an issue when setting up my chef server. I am trying to create an admin user with the command
sudo chef-server-ctl user-create admin Admin Ladmin admin#example.com
examplepass -f admin.pem
but after I keep getting this error:
ERROR: Connection refused connecting...
ERROR: Connection refused connecting to https://127.0.0.1/users/, retry 5/5
ERROR: Network Error: Connection refused - Connection refused
connecting to https://..., giving up
Check your knife configuration and network settings
I also noticed that when I ran chef-server-ctl I got this output:
[2016-12-21T13:24:59-05:00] ERROR: Running exception handlers Running
handlers complete
[2016-12-21T13:24:59-05:00] ERROR: Exception
handlers complete Chef Client failed. 0 resources updated in 01 seconds
[2016-12-21T13:24:59-05:00] FATAL: Stacktrace dumped to
/var/opt/opscode/local-mode-cache/chef-stacktrace.out
[2016-12-21T13:24:59-05:00] FATAL: Please provide the contents of the
stacktrace.out file if you file a bug report
[2016-12-21T13:24:59-05:00] FATAL:
Chef::Exceptions::CannotDetermineNodeName: Unable to determine node
name: configure node_name or configure the system's hostname and fqdn
I read that this error is due to a prerequisite mistake but I'm uncertain as to what it means or how to fix it. So any input would be greatly appreciated.
Your server does not have a valid FQDN (aka full host name). You'll have to fix this before installing Chef server.

Apache Spark compile failed while installing Netty

We untar spark-0.9.0-incubating.tgz and trying to build it for use with Yarn.
SPARK_HADOOP_VERSION=2.0.0-cdh4.6.0 SPARK_YARN=true sbt/sbt assembly
...
[info] Resolving io.netty#netty-all;4.0.13.Final ...
[error] Server access Error: Connection timed out url=https://oss.sonatype.org/content/repositories/snapshots/io/netty/netty-all/4.0.13.Final/netty-all-4.0.13.Final.pom
[error] Server access Error: Connection timed out url=https://oss.sonatype.org/service/local/staging/deploy/maven2/io/netty/netty-all/4.0.13.Final/netty-all-4.0.13.Final.pom
...
If I just cut-paste the url into a browser, I get:
404 - ItemNotFoundException
Retrieval of /io/netty/netty-all/4.0.13.Final/netty-all-4.0.13.Final.pom from M2Repository(id=snapshots) is forbidden by repository policy SNAPSHOT.
org.sonatype.nexus.proxy.ItemNotFoundException: Retrieval of /io/netty/netty-all/4.0.13.Final/netty-all-4.0.13.Final.pom from M2Repository(id=snapshots) is forbidden by repository policy SNAPSHOT.
at org.sonatype.nexus.proxy.maven.AbstractMavenRepository.doRetrieveItem(AbstractMavenRepository.java:380)
at org.sonatype.nexus.proxy.maven.maven2.M2Repository.doRetrieveItem(M2Repository.java:396)
at org.sonatype.nexus.proxy.repository.AbstractRepository.retrieveItem(AbstractRepository.java:765)
at org.sonatype.nexus.proxy.repository.AbstractRepository.retrieveItem(AbstractRepository.java:608)
at org.sonatype.nexus.proxy.router.DefaultRepositoryRouter.retrieveItem(DefaultRepositoryRouter.java:155)
at org.sonatype.nexus.web.content.NexusContentServlet.doGet(NexusContentServlet.java:359)
at org.sonatype.nexus.web.content.NexusContentServlet.service(NexusContentServlet.java:331)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:848)
I have seen this reported in a number of places but no solution. Is this error because we are behind a corporate firewall, or is this due to something else? Please advise.
I had proxy set as environment variables, but it appears they are not being picked up. Adding them in sbt directly worked for me.
Edit $SPARK_HOME/sbt/sbt
For example,
EXTRA_ARGS="-Dhttp.proxySet=true -Dhttp.proxyHost=myproxy.mycompany.com -Dhttp.proxyPort=80 -Dhttps.proxySet=true -Dhttps.proxyHost=myproxy.mycompany.com -Dhttps.proxyPort=80 -Dftp.proxySet=true -Dftp.proxyHost=myproxy.mycompany.com -Dftp.proxyPort=80 -Dhttp.nonProxyHosts=mydomain -Dhttps.nonProxyHosts=mydomain -Dftp.nonProxyHosts=mydomain"

Nginx sends status 200 after PHP parse error

I've configured nginx with php-fpm on Ubuntu (and everything works pretty well).
One thing I encountered is that HTTP status code 200 is sent, when a PHP parse error occurs. The error log contains the following entry:
[error] 3205#0: *2854 FastCGI sent in stderr: "PHP Parse error: syntax error, unexpected T_REQUIRE_ONCE in /var/www/.../index.php on line 32" while reading response header from upstream, client: 1.2.3.4, server: example.com; request: "GET / HTTP/1.1", upstream: "fastcgi://127.0.0.1:9000", host: "example.com"
I was not able to figure out, why not a code 50x is sent. I have not configured any error_page settings and I read the documentation of error_page. I also tried it to set the status code (with error_page 500 =500 /50x.html and so on). But always status 200 is returned.
I can send status headers from PHP (header('HTTP/1.1 404 Not Found')), this works. However, for errors issued by the PHP interpreter (also uncaught exceptions), the server's response doesn't take into account that an error occurred.
FYI, this is now fixed in Xdebug (2.2) for PHP 5.4 and up. Sadly, it needed a change in PHP to make it work that could not be back-ported to 5.3.

Resources