I am trying to install flink on windows running into all sorts of problems . Please help.
Downloading the tar file from net, does not give me windows bat file options. Used the download links at https://flink.apache.org/downloads.html#apache-flink-1111. So i cannot run start-local.bat. Infact i dont even have start-local.sh . I ended up installing cygwin just so i can run start cluster bat
However running the start cluster bat is giving weird issues and exiting immediately.
$ ./start-cluster.sh
Starting cluster.
Starting standalonesession daemon on host DESKTOP**.
Starting taskexecutor daemon on host DESKTOP**.
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
Improperly specified VM option 'MaxMetaspaceSize=268435456
'
This is an open bug for sometime and is deferred to Flink 1.14 version.
https://issues.apache.org/jira/browse/FLINK-18438
https://issues.apache.org/jira/browse/FLINK-18792
When running a build on a newly installed Jenkins server on centos7 The Xvfb fails with the following:
Xvfb starting$ /bin/Xvfb -displayfd 2 -screen 0 1024x768x8 -fbdir
/var/lib/jenkins/xvfb-272-..fbdir6345857630426455925 FATAL: Cannot run
program "/bin/Xvfb": error=2, No such file or directory
java.io.IOException: error=2, No such file or directory
Compared to our original server, the name of the fmdir is different. I believe it should be in the format /var/lib/jenkins/xvfb-<build no.>-<unique number>.fmdir
How is the -fbdir name being generated and what creates the directory?
This is on Jenkins
2.176.1 with Xvfb plugin 1.1.3 on Centos 7.6.1810
Xvfb starting$ /usr/bin/Xvfb -displayfd 2 -screen 0
1920x1080x24 -fbdir /var/lib/jenkins/xvfb-
214-..fbdir17701667040157463918
How is the -fbdir name being generated?
It's unique & random and the format is
/var/lib/jenkins/xvfb-<build no.>-..fbdir<random unique no.>
what creates the directory?
When job is executed, Jenkins check the Directory in which to find Xvfb executable i.e./usr/bin and it creates it's copy for it's use ( at location where Jenkins is installed i.e./var/lib/jenkins/xvfb-214-..fbdir17701667040157463918) where the memory mapped files containing the framebuffer memory should be created to perform all GUI operations in virtual memory.
-fbdir framebuffer-directory
This option specifies the directory in which the memory mapped files containing the framebuffer memory should be created.This option only exists on machines that have the mmap and msync system calls.
Refer:https://docs.oracle.com/cd/E86824_01/html/E54763/xvfb-1.html
Currently trying to open the file gives this error:
C:\Users\....\....\apache-tomcat-8.0.45\logs>catalina.out
The process cannot access the file because it is being used by another process.
What I have done is to have application running in the webapps and start tomcat by using following command:
catalina.bat jpda start
And now I want to see the logs in windows. In Ubuntu, tail -f catalina.out can be used. But how to see tomcat logs in windows forcefully?
As stated in answers here, you can try more catalina.out or type catalina.out
I'm using CentOS 7. My ORACLE_HOME and ORACLE_XE is properly set. Yet when I try to configure my oracle 11g, I get the following error:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux-x86_64 Error: 2: No such file or directory
LRM-00116: syntax error at 'sessions' following '='
ORA-01078: failure in processing system parameters
I'm configuring using /etc/init.d/oracle-xe command.
Please help.
ORACLE_HOME=/u01/app/oracle/product/11.2.0/xe
ORACLE_SID= XE
Below are the steps we should take to ensure the correct installation and Configuration of Oracle XE on CentOS 7
Install libaio1, bc (yum install libaio1 and yum install bc)
Allocate a proper swap space
Set ORACLE_HOME and ORACLE_SID
Check is your IP and hostname is present in /etc/hosts file.
Other than this, https://oracle-base.com/articles/11g/oracle-db-11gr2-installation-on-oracle-linux-7 gives a good checklist but the above 4 MUST be done.
I was facing this issue because Bouncy Castle was not installed
I've set up an App Engine project locally using Docker (on OSX), and have been running a server using the usual "gcloud preview app run app.yaml" command. From what I can tell, this keeps creating new images over and over again. After an hour or so of work I end up with something like 30 docker images, each taking 130MB.
Eventually I'm told I can no longer bind to localhost:8080. I tried killing all containers and images, but still cannot use localhost:8080 until I reboot.
Seems like I'm not using Docker/gcloud correctly. Anyone have an idea what I might be doing wrong? Is there another way I should be restarting App Engine instances other than hitting command C and running the "run" command again?
UPDATE: After looking closer, I noticed I'm getting this message when I run an app locally and a container is created: "http: Hijack is incompatible with use of CloseNotifier". I'm not familiar enough with Docker to understand what's going on here. All searches seem to point to Go, which I am not using.
UPDATE 2: Here is the trace:
Creating container...
INFO 2015-05-05 02:23:28,293 containers.py:560] Container 1564ce4344957114312d6d1dc696ffbb4176b40ace6dcff5e4239e13ee04a8f6 created.
Exception in thread Thread-2:
Traceback (most recent call last):
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 810, in __bootstrap_inner
self.run()
File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 763, in run
self.__target(*self.__args, **self.__kwargs)
File "/Users/judeosborn/google-cloud-sdk/platform/google_appengine/google/appengine/tools/docker/containers.py", line 643, in _ListenToLogs
for line in log_lines:
File "/Users/judeosborn/google-cloud-sdk/./lib/docker/docker/client.py", line 225, in _multiplexed_response_stream_helper
socket = self._get_raw_response_socket(response)
File "/Users/judeosborn/google-cloud-sdk/./lib/docker/docker/client.py", line 167, in _get_raw_response_socket
self._raise_for_status(response)
File "/Users/judeosborn/google-cloud-sdk/./lib/docker/docker/client.py", line 119, in _raise_for_status
raise errors.APIError(e, response, explanation=explanation)
APIError: 500 Server Error: Internal Server Error ("http: Hijack is incompatible with use of CloseNotifier")
INFO 2015-05-05 02:23:28,606 module.py:1745] New instance for module "default" serving on:
http://localhost:8080
There's an ongoing issue with Docker 1.6.x [reference] that prevents gcloud to work well with Managed VMs (as you seem to be using). Easiest workaround until it gets fixed is to downgrade Docker in your development machine to version 1.5.0, which is the latest version known to work.
For Ubuntu, you can do something like:
$ curl -sSL https://get.docker.com/ubuntu | sed 's/lxc-docker/lxc-docker-1.5.0/' | sudo sh
For other Linux distros, you might have to modify that sed pattern, though.
On the other hand, if you're using Boot2Docker under Mac OS X, follow these steps:
Fully uninstall your previous Boot2Docker/Docker setup; there is a nice guide here
Reinstall Boot2Docker/Docker following instructions here. IMPORTANT: You MUST stop right after completing "Install Boot2Docker" step and before "Start the Boot2Docker Application". Once you get there, open up a terminal and execute the following commands:
$ mkdir ~/.boot2docker
$ echo 'ISOURL="https://github.com/boot2docker/boot2docker/releases/download/v1.5.0/boot2docker.iso"' > ~/.boot2docker/profile
At this point, you can continue with "Start the Boot2Docker Application" section and finish the installation. You should now have a valid Docker launchpad with which to start Managed VMs. It'd be nice to double check that you have the right versions installed by issuing:
$ boot2docker ssh docker version | egrep "(Client|Server) version"
The output should look like:
Client version: 1.5.0
Server version: 1.5.0
Now you can try again your original command:
$ gcloud preview app run app.yaml
Try running:
$ ps uax | egrep "gcloud|appserver"
If you see anything running, kill it... you may even need to kill -9 it.