I moved from mod_php to fcgi style hosting and got the following in Apache error log when I tried to open one of my websites: [Tue Nov 08 08:34:08.357359 2022] [core:alert] [pid 19149] [client 95.158.43.63:14405] /home/domain.com/public_html/.htaccess: Option All not allowed here [Tue Nov 08 08:35:58.058962 2022] [core:alert] [pid 14190] [client 95.158.43.63:46366] /home/domain.com/public_html/.htaccess: Option FollowSymlinks not …
Tag: error
Oct 28 2022
Git Error cloning remote repo code 128 early eof
In case you cannot clone your repository even in shallow mode it means that more memory is needed for git to fetch the files. The git output is similar to:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 |
ERROR: Timeout after 10 minutes ERROR: Error cloning remote repo 'origin' git fetch --tags --progress --depth=1 -- git@bitbucket.org:username/repo.git +refs/heads/*:refs/remotes/origin/*" returned status code 128: stdout: stderr: remote: Enumerating objects: 13045, done. remote: Counting objects: 0% (1/13045) remote: Counting objects: 1% (131/13045) ... Receiving objects: 98% (12804/13045), 360.22 MiB | 635.00 KiB/s Receiving objects: 98% (12804/13045), 360.95 MiB | 643.00 KiB/s fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed |
Again we see the same fatal: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed
Aug 26 2022
key type ssh-rsa not in pubkey accepted algorithms
I was running Ubuntu 20.04 happily, and then over the weekend decided to back everything up and install 22.04. I installed my previous keys but I couldn’t login via MobaXTerm remotely as I usually did with 20.04. I logged in with a console and checked /var/log/auth.log . Here are the messages generated upon my tries …
Aug 12 2022
Jenkins: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed
Again the same git error: The remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed. This time – during the execution of Jenkins pipeline:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 |
ssh_dispatch_run_fatal: Connection to 104.10.141.1 port 22: message authentication code incorrect fatal: the remote end hung up unexpectedly fatal: early EOF fatal: index-pack failed warning: unable to unlink '(NULL)': Invalid argument at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2681) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandWithCredentials(CliGitAPIImpl.java:2102) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.access$500(CliGitAPIImpl.java:86) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$1.execute(CliGitAPIImpl.java:624) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:853) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:160) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$GitCommandMasterToSlaveCallable.call(RemoteGitImpl.java:153) at hudson.remoting.UserRequest.perform(UserRequest.java:211) at hudson.remoting.UserRequest.perform(UserRequest.java:54) at hudson.remoting.Request$2.run(Request.java:375) at hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:73) at java.util.concurrent.FutureTask.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:118) at java.lang.Thread.run(Unknown Source) Suppressed: hudson.remoting.Channel$CallSiteStackTrace: Remote call to JNLP4-connect connection from 192.168.2.90/192.168.2.90:477 at hudson.remoting.Channel.attachCallSiteStackTrace(Channel.java:1784) at hudson.remoting.UserRequest$ExceptionResponse.retrieve(UserRequest.java:356) at hudson.remoting.Channel.call(Channel.java:1000) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.execute(RemoteGitImpl.java:145) at jdk.internal.reflect.GeneratedMethodAccessor1213.invoke(Unknown Source) at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.base/java.lang.reflect.Method.invoke(Method.java:566) at org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler.invoke(RemoteGitImpl.java:131) at com.sun.proxy.$Proxy76.execute(Unknown Source) at hudson.plugins.git.GitSCM.retrieveChanges(GitSCM.java:1224) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1302) at hudson.scm.SCM.checkout(SCM.java:540) at hudson.model.AbstractProject.checkout(AbstractProject.java:1217) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:647) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:85) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:519) at hudson.model.Run.execute(Run.java:1897) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:44) at hudson.model.ResourceController.execute(ResourceController.java:101) at hudson.model.Executor.run(Executor.java:442) ERROR: Error cloning remote repo 'origin' Finished: FAILURE |
Apr 11 2022
CentOS7 dockerError while creating filesystem xfs on device docker exit status 1
When you try to start docker it exits with exit status 1.
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 |
[root@localhost ~]# systemctl start docker Job for docker.service failed because the control process exited with error code. See "systemctl status docker.service" and "journalctl -xe" for details. [root@localhost ~]# systemctl status -l docker ● docker.service - Docker Application Container Engine Loaded: loaded (/usr/lib/systemd/system/docker.service; disabled; vendor preset: disabled) Active: failed (Result: start-limit) since 四 2020-05-14 11:02:36 CST; 5s ago Docs: https://docs.docker.com Process: 6732 ExecStart=/usr/bin/dockerd (code=exited, status=1/FAILURE) Main PID: 6732 (code=exited, status=1/FAILURE) 5月 14 11:02:36 localhost.localdomain systemd[1]: Failed to start Docker Application Container Engine. 5月 14 11:02:36 localhost.localdomain systemd[1]: Unit docker.service entered failed state. 5月 14 11:02:36 localhost.localdomain systemd[1]: docker.service failed. 5月 14 11:02:36 localhost.localdomain systemd[1]: docker.service holdoff time over, scheduling restart. 5月 14 11:02:36 localhost.localdomain systemd[1]: Stopped Docker Application Container Engine. 5月 14 11:02:36 localhost.localdomain systemd[1]: start request repeated too quickly for docker.service 5月 14 11:02:36 localhost.localdomain systemd[1]: Failed to start Docker Application Container Engine. 5月 14 11:02:36 localhost.localdomain systemd[1]: Unit docker.service entered failed state. 5月 14 11:02:36 localhost.localdomain systemd[1]: docker.service failed. |
In /var/log/messages you can find the following:
Mar 18 2022
Couldn’t add sdp streams for stream
You try to establsish a call but it got disconnected and there is following message in Asterisk console from PJSIP Couldn’t add sdp streams for stream:
|
1 |
res_pjsip_session.c:5160 create_local_sdp: PJSIP/teams_out-0000000b: Couldn't add sdp streams for stream 0:audio-0:audio:sendrecv (ulaw|alaw|gsm) |
Two most common cases can cause this:
Mar 12 2022
An error occurred within the report server database. This may be due to a connection failure, timeout or low disk condition within the database
I had this issue due to having the Reporting Services databases in an Availability Group. When we failed over (for the first time) there were a bunch of permissions not correctly set, specifically the RSExecRole was not there. The reports worked, but not the subscriptions and we couldn’t edit any of the report settings. Upon …
Feb 19 2022
MariaDB error InnoDB: Upgrade after a crash is not supported
Here is a crash I experienced while upgrading MariaDB from 10.4 to 10.5
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 |
● mariadb.service - MariaDB 10.5.5 database server Loaded: loaded (/usr/lib/systemd/system/mariadb.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Sun 2020-09-27 14:57:13 CEST; 12min ago Docs: man:mariadbd(8) https://mariadb.com/kb/en/library/systemd/ Main PID: 194683 (code=exited, status=1/FAILURE) Status: "MariaDB server is down" sept. 27 14:57:13 massine-pc mariadbd[194683]: 2020-09-27 14:57:13 0 [ERROR] InnoDB: Upgrade after a crash is not supported. The redo log was created with MariaDB 10.4.12. sept. 27 14:57:13 massine-pc mariadbd[194683]: 2020-09-27 14:57:13 0 [ERROR] InnoDB: Plugin initialization aborted with error Generic error sept. 27 14:57:13 massine-pc mariadbd[194683]: 2020-09-27 14:57:13 0 [Note] InnoDB: Starting shutdown... sept. 27 14:57:13 massine-pc mariadbd[194683]: 2020-09-27 14:57:13 0 [ERROR] Plugin 'InnoDB' init function returned error. sept. 27 14:57:13 massine-pc mariadbd[194683]: 2020-09-27 14:57:13 0 [ERROR] Plugin 'InnoDB' registration as a STORAGE ENGINE failed. sept. 27 14:57:13 massine-pc mariadbd[194683]: 2020-09-27 14:57:13 0 [ERROR] Unknown/unsupported storage engine: InnoDB sept. 27 14:57:13 massine-pc mariadbd[194683]: 2020-09-27 14:57:13 0 [ERROR] Aborting sept. 27 14:57:13 massine-pc systemd[1]: mariadb.service: Main process exited, code=exited, status=1/FAILURE sept. 27 14:57:13 massine-pc systemd[1]: mariadb.service: Failed with result 'exit-code'. sept. 27 14:57:13 massine-pc systemd[1]: Failed to start MariaDB 10.5.5 database server. |
Jan 22 2022
Roundcube: SMTP server does not support authentication
When I try to send a letter from Roundcube I get the following error:
|
1 |
Authentication failure: SMTP server does not support authentication (Code: )) |
This can happen if Postfix doesn’t allow authentication from a localhost where Roundcube resides or if authentication scheme is wrong.
Jan 08 2022
SSRS Something went wrong. Try again later
This annoying error was discovered when I tried to modify subscription settings for one of the reports that I have on SQL Reporting Server 2016. When you look inside of your Report Server Error Logs, you see the following error: ERROR: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS …
Stay tuned! :)
