What does [unknown]@[unknown] LOG: incomplete startup packet mean?

I am having troubles with starting Kong with Postgres. I inspected my desktop’s log

root@miki:/var/log/postgresql# 2019-04-22 07:35:28.040 CEST [1181] LOG:  listening on IPv4 address "", port 5432 2019-04-22 07:35:28.070 CEST [1181] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432" 2019-04-22 07:35:28.438 CEST [1426] LOG:  database system was shut down at 2019-04-21 20:13:57 CEST 2019-04-22 07:35:28.546 CEST [1181] LOG:  database system is ready to accept connections 2019-04-22 07:35:29.175 CEST [1690] [unknown]@[unknown] LOG:  incomplete startup packet 

What does this mean?

My postgresql is running

/etc/init.d/postgresql status ● postgresql.service - PostgreSQL RDBMS    Loaded: loaded (/lib/systemd/system/postgresql.service; enabled; vendor preset: enabled)    Active: active (exited) since Mon 2019-04-22 07:35:30 CEST; 1h 45min ago   Process: 1939 ExecStart=/bin/true (code=exited, status=0/SUCCESS)  Main PID: 1939 (code=exited, status=0/SUCCESS)  апр 22 07:35:30 miki systemd[1]: Starting PostgreSQL RDBMS... апр 22 07:35:30 miki systemd[1]: Started PostgreSQL RDBMS. 

How to set .sh file to execute on startup on Ubuntu in VirtualBox?

VirutalBox Ubuntu sets default resolution on every launch. Found a comment in a topic here on how to create a .sh file, said also to add it in Startup Applications. But on reboot the .sh file didn’t execute and even was removed from the Startup Applications list, there was one entry that I’ve added but it had blank fields.

The comment also said to set the .sh file as executable and double click it, but it still opened in text editor for me so each time I had to execute it through the terminal.

Bitlocker, does additional authentication at startup with TPM device provide any extra security?

Will enabling additional authentication on startup provide any extra security with Bitlocker? At the moment, my laptop boots straight into a Windows login where I use a pin. If I chose to not use pin, and a complex password, would that provide the same level of security as authentication at startup?


Cyclic startup problems (black screen -> superblock checksum wrong -> kernel panic after e2fsck -> ok startup -> black screen -> …)

I have these problems on every boot. Basically, the booting my system acts like a state machine.

The first state is booting into a black screen. I’m forced to power the PC off.

After this, the next boot results in e2fsck detecting a problem with the superblock checksum. The message is below (I apologize for taking pictures of the screen with my phone, but I have no way of taking a screenshot in this state, as you might guess):

enter image description here

As shown, I run an e2fsck -b 32768 /dev/sda11 -y

The result of this is the following – directories, free inodes counts wrong => file system modified (and the values are identical on every startup):

enter image description here

I type exit after this, and get this kernel panic message:

enter image description here

This forces me to power off the PC again. However, the next boot works just fine and I get into the system.

Unfortunately, the moment I turn the PC off and want to boot again, I revert back to the first state, basically forcing me to go through this whole procedure every time I want to boot. How can I fix this permanently? Maybe this could somehow be related to the fact that I have a hybrid hard drive?

Entity Framework 6 startup performance in SaaS environment/scenario

We use EF6.2 in our Web SaaS application. We have database per account architecture which means every customer gets separate SQL Server database.

What we see is extremely slow startups. We also see startups getting proportionaly slower with amount of accounts we add.

We currently do not use any of optimizations possible. We don’t do ngen, we don’t “pre-compile” views. But what bothers me is that it’s not performance hit we take overall, but per account.

That leads me to beleive it is related to metadata cache which according to article here being built in-memory and tagged with hash derived from connection string.

Looking for any suggestions on how to reduce “warm up” time to single occurence

Computer unable to boot to windows 7 Home Premium, and instead opens up Startup Repair

Every time I boot my dell PC it opens Startup Repair and can’t repair the computer.I am don’t know ho to fix it. I get the following Problem Signatures:

Problem Event name: StartupRepairOffline

Problem Signature 01: 6.1.7600.16385

Problem Signature 02: 6.1.7600.16385

Problem Signature 03: unknown

Problem Signature 04: 21200281

Problem Signature 05: AutoFailover

Problem Signature 06: 12

Problem Signature 07: NoRootCause

OS Version: 6.1.6700.