Category Archives: How to Fix

Error kernel restart: restart failed was reported in the background of jupyter notebook

after successful installation by PIP install jupyter In the CMD window, run the jupyter notebook, and it was found that the left side of the code In [] changed to In [*], and the error was reported In the CMD window as follows:

KernelRestarter: restart failed. Kernel restart failed

solution: PIP install –upgrade ipykernel will upgrade it can run normally, although it will prompt you prompt toolkit version should be between 1.0 and 2.0, but it does not affect the operation of prompyter notebook. In the upgrade process, the main updated module is the prompt_toolkit, it seems that because the version of this module is too low, it leads to

QE-DEF-0285 The logon failed–windows

On June 12, 2018, it was found that some models could be brushed, some could not be brushed, and the error message that could not be brushed was as follows:

qe-def-0285 The logon failed.

QE-DEF-0323 The DSN(ODBC)/ServiceName is invalid. Either the DSN is missing or the host is inaccessible.

RQP-DEF-0068 Unable to connect to at least one database during a multi-database attach to 1 database(s) in: COGNOS

UDA-SQL-0031 Unable to access the “COGNOS” database.

UDA-SQL-0532 Data Source is not accessible: “OPYTF”.

[Microsoft][ODBC driver manager] did not find data source name and did not specify default driver

[Microsoft][ODBC driver manager] invalid connection string attribute

reason: went to freamwork and found that the data source COGNOS connection is not working. Models made with freamwork cannot be brushed. Models made with iqd files can be brushed with

solution: changes the JDBC connection in the configured data source to DB2 connection

Failed to resolve: com.android.support:appcompat-v7:27.

I think many novices using AndroidStudio will run into the following problem the first time they start a new project:

[problem description]

for this problem, I think if I don’t know the solution, I will install the relevant plug-in

as shown in the following diagram

well, I’m not going to say any more nonsense about this kind of problem and I’m going to go straight to my solution, which is

[solution]

1. Click on the File – & gt; Settings appear as shown below

and then let’s look at the bottom red line that I drew, these two represent our SDK model and Android API version

2. We switch our process items from Android– > Project, then click builde.gradle

in the red line box as shown below

appears as follows

what I’m drawing in the figure above is the thing that we’re going to change because we just saw that our SDK version is 26 so we just change the red line from 27 to 26 in the figure like this

then click Try Again as shown above. Wait a moment, and the problem will be solved.

and then we’re done. Isn’t that easy?If you need more learning resources, please pay attention to the public number in the upper left corner.

Ubuntu: Failed to initialize compiler: object java.lang.Object In compiler mirror not found

haven’t used spark for a long time. Today, log on the Ubuntu system remotely and execute./spark-shell report error “Failed to initialize compiler: object java.lang. object in compiler mirror not found”.

looked at the Java installation version, there is no problem, so check the ~/.bashrc file, found that the Java path is not, rewrote it is OK.

Use NVIDIA to solve NVIDIA’s

used to display memory usage successfully using the nvidia-smi command, but not recently,
NVIDIA-SMI has failed because it couldn’t communicate with the NVIDIA driver. Make sure that the latest NVIDIA driver is installed and running. And others said it is ok to install the driver again, these are not solve my problem, actually very simple question because ubutnu kernel update, a new version of the kernel and graphics driver does not match the above problems, we need only when making ubuntu startup guide interface, is just began to call you to select the operating system interface, select “ubuntu advanced options”, select a previous version of the kernel, is the new version of my 4.15.0-43 – generic
I then chose 4.15.0-42 – generic version, Then enter the system and use the nvidia-SMi command to execute successfully.
you can view the current ubuntu kernel version

using the following command

>uname -r

Android Error | Failed to find target with hash string ”android-23′ in…

downloaded a project on github today, opened it up and ran android studio, configuration failed.

1. Component download failed

gradle automatic configuration file, need to download some components, it is estimated that some of the components of this project download address is access to the external network… This problem is solved by connecting the external network VPN and reconfiguring it

2.

search, this should be caused by the inconsistency of the built-in SDK platform version of android, my version in android studio is not consistent with this project…

we can see from the error message that this project needs android-23, but I did not install it. The solution:

1. Open android SDK manager:

2, click “show package details” in the lower right corner, select all components related to android-23, apply:

3, waiting to download

3, supplement

actually the configured version can be found on github, next time you download the configuration, you can look at the version, make sure the package version is available before you start the configuration!

also can not download so many versions of the method (it is really time and space consuming) can see the details of this article: Android learning notes | 2.2 migration of the old version of Android project

“DNET: failed to open device eth1” error resolution of nmap

0 x00: problems

to learn the use of the system nmap, run a simple command :

nmap -sC -p1- www.landgrey.cn

error: “dnet: Failed to open device eth1”
has not reported such a mistake before, I checked the data, found that it is likely to be related to winpcap drive .

0x01: resolution

and then downloaded
Win10Pcap 10.2.5002 Windows 32bit and 64bit Installer
after the installation, found the scanning process reported another error…… 

FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.
FATAL Bad Memory Block.

is installing two winpcap incompatible?Uninstall the old version of winpcap, and then uninstall after what seems to remind, also did not pay attention to, it automatically ignored ~
and then run again, found that I did not install winpcap, it seems that this Win10Pcap not ah, and then uninstall Win10Pcap, there is a reminder when uninstall, this time just think of carefully look, found is not found when uninstall 

C:\Windows\SysWOW64\Packet.dll

find Packet. DLL changed to Packet. DLL. Bak… Nima, also do not know is the ghost that anti-virus software makes, after restoring original name, hint did not find

again

C:\Windows\SysWOW64\wpcap.dll

a check found that the name is also changed to wpcap.dll. Bak. After the recovery, the normal uninstall.
then go to the official website to download the latest version of wincap

After the

installation, run the original command and find that the problem has been resolved.

nmap – sT 192.168.0.184 

Stats: 0:00:03 elapsed; 0 hosts completed (1 up), 1 undergoing Connect Scan
Connect Scan Timing: About 4.85% done; ETC: 16:22 (0:00:39 remaining)
Nmap scan report for 192.168.0.184
Host is up (0.00071s latency).
Not shown: 991 filtered ports
PORT    STATE SERVICE
25/tcp  open  smtp
110/tcp open  pop3
119/tcp open  nntp
143/tcp open  imap
465/tcp open  smtps
563/tcp open  snews
587/tcp open  submission
993/tcp open  imaps
995/tcp open  pop3s

0 x02: postscript

must not ignore some important tips to solve the problem in the process of solving the problem because of haste.
also do not know how DLL file into DLL. Bak file, fortunately did not give me delete ×_×

RTMP_Connect0, failed to connect socket. 110 (Connection timed out)

perform ffmpeg – re – I/var/WWW/HTML/input. Mp4 – vprofile baseline – acodec aac – ar 44100 – strict – 2-1 – f ac FLV -s 1280 x720 – q 10 RTMP:// XXX. XXX. XXX. XXX: 1935/HLS RTMP_Connect0
appeared, Failed to connect socket. 110 (Connection Timed out) error.

processing:
ali cloud machine port 1935 is not open.

A child container failed during start

error starting Tomcat, complete information is as follows: 

严重: A child container failed during start
java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/WIcket-Learn]]
	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
	at java.util.concurrent.FutureTask.get(FutureTask.java:188)
	at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:916)
	at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:871)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost].StandardContext[/WIcket-Learn]]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:153)
	... 6 more
Caused by: java.lang.IllegalArgumentException: Filter mapping specifies an unknown filter name DempApplication
	at org.apache.catalina.core.StandardContext.validateFilterMap(StandardContext.java:2944)
	at org.apache.catalina.core.StandardContext.addFilterMap(StandardContext.java:2909)
	at org.apache.catalina.startup.ContextConfig.configureContext(ContextConfig.java:1275)
	at org.apache.catalina.startup.ContextConfig.webConfig(ContextConfig.java:1184)
	at org.apache.catalina.startup.ContextConfig.configureStart(ContextConfig.java:779)
	at org.apache.catalina.startup.ContextConfig.lifecycleEvent(ContextConfig.java:306)
	at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:95)
	at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
	at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5150)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
	... 6 more

五月 03, 2017 4:06:10 下午 org.apache.catalina.core.ContainerBase startInternal
严重: A child container failed during start
java.util.concurrent.ExecutionException: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost]]
	at java.util.concurrent.FutureTask.report(FutureTask.java:122)
	at java.util.concurrent.FutureTask.get(FutureTask.java:188)
	at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:916)
	at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
	at org.apache.catalina.core.StandardService.startInternal(StandardService.java:441)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
	at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:787)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
	at org.apache.catalina.startup.Catalina.start(Catalina.java:629)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:351)
	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:485)
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina].StandardHost[localhost]]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:153)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1408)
	at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1398)
	at java.util.concurrent.FutureTask.run(FutureTask.java:262)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
	at java.lang.Thread.run(Thread.java:745)
Caused by: org.apache.catalina.LifecycleException: A child container failed during start
	at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:924)
	at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:871)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
	... 6 more

五月 03, 2017 4:06:10 下午 org.apache.catalina.startup.Catalina start
严重: The required Server component failed to start so Tomcat is unable to start.
org.apache.catalina.LifecycleException: Failed to start component [StandardServer[8005]]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:153)
	at org.apache.catalina.startup.Catalina.start(Catalina.java:629)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:351)
	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:485)
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardService[Catalina]]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:153)
	at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:787)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
	... 7 more
Caused by: org.apache.catalina.LifecycleException: Failed to start component [StandardEngine[Catalina]]
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:153)
	at org.apache.catalina.core.StandardService.startInternal(StandardService.java:441)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
	... 9 more
Caused by: org.apache.catalina.LifecycleException: A child container failed during start
	at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:924)
	at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262)
	at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)
	... 11 more

五月 03, 2017 4:06:10 下午 org.apache.coyote.AbstractProtocol pause
信息: Pausing ProtocolHandler ["http-nio-8080"]
五月 03, 2017 4:06:10 下午 org.apache.coyote.AbstractProtocol pause
信息: Pausing ProtocolHandler ["ajp-nio-8009"]
五月 03, 2017 4:06:10 下午 org.apache.catalina.core.StandardService stopInternal
信息: Stopping service Catalina
五月 03, 2017 4:06:10 下午 org.apache.coyote.AbstractProtocol destroy
信息: Destroying ProtocolHandler ["http-nio-8080"]
五月 03, 2017 4:06:10 下午 org.apache.coyote.AbstractProtocol destroy
严重: Failed to destroy end point associated with ProtocolHandler ["http-nio-8080"]
java.lang.NullPointerException
	at org.apache.tomcat.util.net.NioEndpoint.releaseCaches(NioEndpoint.java:305)
	at org.apache.tomcat.util.net.NioEndpoint.unbind(NioEndpoint.java:481)
	at org.apache.tomcat.util.net.AbstractEndpoint.destroy(AbstractEndpoint.java:831)
	at org.apache.coyote.AbstractProtocol.destroy(AbstractProtocol.java:533)
	at org.apache.catalina.connector.Connector.destroyInternal(Connector.java:1023)
	at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:297)
	at org.apache.catalina.core.StandardService.destroyInternal(StandardService.java:589)
	at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:297)
	at org.apache.catalina.core.StandardServer.destroyInternal(StandardServer.java:877)
	at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:297)
	at org.apache.catalina.startup.Catalina.start(Catalina.java:633)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:351)
	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:485)

五月 03, 2017 4:06:10 下午 org.apache.coyote.AbstractProtocol destroy
信息: Destroying ProtocolHandler ["ajp-nio-8009"]
五月 03, 2017 4:06:10 下午 org.apache.coyote.AbstractProtocol destroy
严重: Failed to destroy end point associated with ProtocolHandler ["ajp-nio-8009"]
java.lang.NullPointerException
	at org.apache.tomcat.util.net.NioEndpoint.releaseCaches(NioEndpoint.java:305)
	at org.apache.tomcat.util.net.NioEndpoint.unbind(NioEndpoint.java:481)
	at org.apache.tomcat.util.net.AbstractEndpoint.destroy(AbstractEndpoint.java:831)
	at org.apache.coyote.AbstractProtocol.destroy(AbstractProtocol.java:533)
	at org.apache.catalina.connector.Connector.destroyInternal(Connector.java:1023)
	at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:297)
	at org.apache.catalina.core.StandardService.destroyInternal(StandardService.java:589)
	at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:297)
	at org.apache.catalina.core.StandardServer.destroyInternal(StandardServer.java:877)
	at org.apache.catalina.util.LifecycleBase.destroy(LifecycleBase.java:297)
	at org.apache.catalina.startup.Catalina.start(Catalina.java:633)
	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
	at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.lang.reflect.Method.invoke(Method.java:606)
	at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:351)
	at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:485)

Finally, I checked that the filter mapping name was misspelled

<filter>
  	<filter-name>DemoApplication</filter-name>
  	<filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class>
  		<init-param>
				<param-name>applicationClassName</param-name>
				<param-value>org.wicket.demo.BookmarkablePageLink.HelloWorldApplication</param-value>  			
  		</init-param>
  </filter>
  
  <filter-mapping>
  	<filter-name>DempApplication</filter-name>
  	<url-pattern>/*</url-pattern>
  </filter-mapping>


Tensorflow error record: depreciation warning: elementwise

when learning simple neural network with tensorflow, the following error is reported:

DeprecationWarning: elementwise == comparison failed; this will raise an error

the reason is: when processing the data, I ran the following code, and then re-pasted a copy, running it again, making the data become three-dimensional, causing the mismatch of the data:

code: 

image_size = 28
num_labels = 10

def reformat(dataset, labels):
  dataset = dataset.reshape((-1, image_size * image_size)).astype(np.float32)
  # Map 0 to [1.0, 0.0, 0.0 ...], 1 to [0.0, 1.0, 0.0 ...]
  labels = (np.arange(num_labels) == labels[:,None]).astype(np.float32)
  return dataset, labels
train_dataset, train_labels = reformat(train_dataset, train_labels)
valid_dataset, valid_labels = reformat(valid_dataset, valid_labels)
test_dataset, test_labels = reformat(test_dataset, test_labels)
print('Training set', train_dataset.shape, train_labels.shape)
print('Validation set', valid_dataset.shape, valid_labels.shape)
print('Test set', test_dataset.shape, test_labels.shape)

correct result: 

Training set (200000, 784) (200000, 10)
Validation set (10000, 784) (10000, 10)
Test set (10000, 784) (10000, 10)

run error result:

Training set (200000, 784) (200000, 1, 10)
Validation set (10000, 784) (10000, 1, 10)
Test set (10000, 784) (10000, 1, 10)

obviously, the dimension of the data is wrong

solution: rerun the first time the program can be allowed only once.