One of my users from Iran is unable to connect to port 80/443 which is open otherwise on the GCP
mtr -rw 35.229.29.0
HOST: ir-hs01.xxxx.com Loss% Snt Last Avg Best Wrst StDev
1. 185-173-105-113.static.hostiran.name 0.0% 10 1.2 0.6 0.3 2.4 0.7
2. 10.201.42.169 0.0% 10 1.1 0.5 0.4 1.1 0.2
3. 10.201.43.1 0.0% 10 2.4 5.1 2.2 26.4 7.5
4. 10.201.22.113 0.0% 10 3.6 2.5 2.2 3.6 0.4
5. 10.202.4.9 0.0% 10 1.6 1.7 1.5 2.0 0.1
6. 10.202.4.77 0.0% 10 1.8 1.9 1.8 2.0 0.1
7. 10.21.21.10 0.0% 10 2.4 2.2 2.0 2.5 0.1
8. 10.21.21.10 0.0% 10 1.9 2.0 1.9 2.3 0.2
9. de-cix.fra.google.com 0.0% 10 73.7 74.8 72.9 90.0 5.4
10. 108.170.251.209 0.0% 10 73.7 73.7 73.6 73.8 0.1
11. 209.85.240.113 0.0% 10 73.5 73.6 73.4 74.0 0.2
12. 216.239.50.187 0.0% 10 83.8 83.8 83.7 84.1 0.1
13. 216.239.54.148 0.0% 10 158.4 158.5 158.2 159.1 0.2
14. 209.85.255.146 0.0% 10 171.2 171.3 171.0 171.6 0.2
15. 72.14.238.123 0.0% 10 170.9 171.2 170.9 172.5 0.5
16. ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
The MTR report shows the traffic is entering Google premium network at France and it gets blocked at a later stage
Why is the IP blocked?
Google restricts access to some of its business services in certain countries according to the following list including Iran.
There is not an official list for Compute Engine. I would recommend using the provided link until one specifically for GCE is created.
Related
I have a problem when installing zabbix as follows. Can someone please point me in the direction how to fix this
dnf install zabbix-server-pgsql zabbix-web-pgsql zabbix-apache-conf zabbix-sql-scripts zabbix-agent
Extra Packages for Enterprise Linux 8 - x86_64 891 kB/s | 10 MB 00:11
Zabbix Official Repository - x86_64 19 kB/s | 29 kB 00:01
CentOS Linux 8 - BaseOS 246 kB/s | 2.6 MB 00:10
Extra Packages for Enterprise Linux Modular 8 - x86_64 429 kB/s | 663 kB 00:01
Zabbix Official Repository non-supported - x86_64 993 B/s | 1.2 kB 00:01
CentOS Linux 8 - AppStream 316 kB/s | 7.5 MB 00:24
CentOS Linux 8 - Extras 18 kB/s | 9.6 kB 00:00
Error:
Problem: conflicting requests
- package zabbix-server-pgsql-5.4.0-8.el8.x86_64 requires libodbc.so.2()(64bit), but none of the providers can be installed
- package zabbix-server-pgsql-5.4.1-1.el8.x86_64 requires libodbc.so.2()(64bit), but none of the providers can be installed
- package unixODBC-2.3.7-1.el8.x86_64 requires libreadline.so.7()(64bit), but none of the providers can be installed
- cannot install both readline-7.0-10.el8.x86_64 and readline-6.2-11.el7.x86_64
- package python-libs-2.7.5-90.el7.x86_64 requires libreadline.so.6()(64bit), but none of the providers can be installed
- problem with installed package python-libs-2.7.5-90.el7.x86_64
I resolved this by reinstalling the Centos 8 from scratch
I have a Intel Xeon machine with NVIDIA GeForce1080 GTX configured and CentOS 7 as operating system. I have installed NVIDIA-driver 410.93 and cuda-toolkit 10.0. After compiling the cuda-samples, i tried to run ./deviceQuery.
But it throws like this
./deviceQuery Starting...
CUDA Device Query (Runtime API) version (CUDART static linking)
cudaGetDeviceCount returned 30
-> unknown error
Result = FAIL
some command outputs
lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GP104 [GeForce GTX 1080] (rev a1)
nvidia-smi
Wed Feb 13 16:08:07 2019
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 410.93 Driver Version: 410.93 CUDA Version: 10.0 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 1080 Off | 00000000:01:00.0 On | N/A |
| 0% 54C P0 46W / 240W | 175MiB / 8119MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 6275 G /usr/bin/X 94MiB |
| 0 7268 G /usr/bin/gnome-shell 77MiB |
+-----------------------------------------------------------------------------+
nvcc --version
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2018 NVIDIA Corporation
Built on Sat_Aug_25_21:08:01_CDT_2018
Cuda compilation tools, release 10.0, V10.0.13
PATH & LD_LIBRARY_PATH
PATH =/usr/local/cuda-10.0/bin:/usr/local/cuda/bin:/usr/local/bin:/usr/local/sbin:
LD_LIBRARY_PATH = /usr/local/cuda-10.0/lib64:/usr/local/cuda/lib64:
lsmod | grep nvidia
nvidia_drm 39819 3
nvidia_modeset 1036573 6 nvidia_drm
nvidia 16628708 273 nvidia_modeset
drm_kms_helper 179394 1 nvidia_drm
drm 429744 6 drm_kms_helper,nvidia_drm
ipmi_msghandler 56032 2 ipmi_devintf,nvidia
lsmod | grep nvidia-uvm
no output
dmesg | grep NVRM
[ 8.237489] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 410.93 Thu Dec 20 17:01:16 CST 2018 (using threaded interrupts)
Is this problem anything related to modprobe or nvidia-uvm?
I asked this in NVIDIA-devtalk forum, but no-reply yet.
Please give some suggestions.
Thanking in advance.
I debugged it. The problem is version mismatch between nvidia-driver(410.93) and cuda(with driver 410.48 came with cuda run file). Gave autoremove all the drivers and reinstalled from the beginning. Deleted all the link files in /var/lib/dkms/nvidia/*.
Now it works fine. And nvidia-uvm also loaded.
lsmod | grep nvidia
nvidia_uvm 786031 0
nvidia_drm 39819 3
nvidia_modeset 1048491 6 nvidia_drm
nvidia 16805034 274 nvidia_modeset,nvidia_uvm
drm_kms_helper 179394 1 nvidia_drm
drm 429744 6 drm_kms_helper,nvidia_drm
ipmi_msghandler 56032 2 ipmi_devintf,nvidia
nvidia-smi
Fri Feb 15 11:46:24 2019
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 410.48 Driver Version: 410.48 |
|-------------------------------+----------------------+----------------------+
| GPU Name Persistence-M| Bus-Id Disp.A | Volatile Uncorr. ECC |
| Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. |
|===============================+======================+======================|
| 0 GeForce GTX 1080 Off | 00000000:01:00.0 On | N/A |
| 0% 45C P8 10W / 240W | 242MiB / 8119MiB | 0% Default |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes: GPU Memory |
| GPU PID Type Process name Usage |
|=============================================================================|
| 0 6063 G /usr/bin/X 120MiB |
| 0 7502 G /usr/bin/gnome-shell 119MiB |
+-----------------------------------------------------------------------------+
nvcc -V
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2018 NVIDIA Corporation
Built on Sat_Aug_25_21:08:01_CDT_2018
Cuda compilation tools, release 10.0, V10.0.130
./deviceQuery
./deviceQuery Starting...
CUDA Device Query (Runtime API) version (CUDART static linking)
Detected 1 CUDA Capable device(s)
Device 0: "GeForce GTX 1080"
CUDA Driver Version / Runtime Version 10.0 / 10.0
CUDA Capability Major/Minor version number: 6.1
Total amount of global memory: 8119 MBytes (8513585152 bytes)
(20) Multiprocessors, (128) CUDA Cores/MP: 2560 CUDA Cores
GPU Max Clock rate: 1797 MHz (1.80 GHz)
Memory Clock rate: 5005 Mhz
Memory Bus Width: 256-bit
L2 Cache Size: 2097152 bytes
Maximum Texture Dimension Size (x,y,z) 1D=(131072), 2D=(131072, 65536), 3D=(16384, 16384, 16384)
Maximum Layered 1D Texture Size, (num) layers 1D=(32768), 2048 layers
Maximum Layered 2D Texture Size, (num) layers 2D=(32768, 32768), 2048 layers
Total amount of constant memory: 65536 bytes
Total amount of shared memory per block: 49152 bytes
Total number of registers available per block: 65536
Warp size: 32
Maximum number of threads per multiprocessor: 2048
Maximum number of threads per block: 1024
Max dimension size of a thread block (x,y,z): (1024, 1024, 64)
Max dimension size of a grid size (x,y,z): (2147483647, 65535, 65535)
Maximum memory pitch: 2147483647 bytes
Texture alignment: 512 bytes
Concurrent copy and kernel execution: Yes with 2 copy engine(s)
Run time limit on kernels: Yes
Integrated GPU sharing Host Memory: No
Support host page-locked memory mapping: Yes
Alignment requirement for Surfaces: Yes
Device has ECC support: Disabled
Device supports Unified Addressing (UVA): Yes
Device supports Compute Preemption: Yes
Supports Cooperative Kernel Launch: Yes
Supports MultiDevice Co-op Kernel Launch: Yes
Device PCI Domain ID / Bus ID / location ID: 0 / 1 / 0
Compute Mode:
< Default (multiple host threads can use ::cudaSetDevice() with device simultaneously) >
deviceQuery, CUDA Driver = CUDART, CUDA Driver Version = 10.0, CUDA Runtime Version = 10.0, NumDevs = 1
Result = PASS
Octave 4.0.0 works on Windows 7 32 bit. I have just downloaded 4.4.1 and it has never worked.
Following information:
Problem signature:
Problem Event Name: APPCRASH
Application Name: octave-gui.exe
Application Version: 0.0.0.0
Application Timestamp: 00000000
Fault Module Name: Qt5Core.dll
Fault Module Version: 5.11.0.0
Fault Module Timestamp: 00000000
Exception Code: 40000015
Exception Offset: 002e8696
OS Version: 6.1.7601.2.1.0.256.48
Locale ID: 3081
Additional Information 1: d1e0
Additional Information 2: d1e00fdc0b78c108f75564157f84c2f0
Additional Information 3: f785
Additional Information 4: f7855e1e76ad3f0614cfa9b98110597e
Found a vaguely similar problem, failing to start GUI on Windows 10, applied suggested solution of setting "Disable display scaling on high DPI settings" under Compatibility tab of executable Properties.
If you download GNU octave from octave.org you'll see a list:
Windows-64 (recommended)
octave-4.4.1-w64-installer.exe (~ 238 MB) [signature]
octave-4.4.1-w64.7z (~ 267 MB) [signature]
octave-4.4.1-w64.zip (~ 481 MB) [signature]
Windows-32 (old computers)
octave-4.4.1-w32-installer.exe (~ 238 MB) [signature]
octave-4.4.1-w32.7z (~ 267 MB) [signature]
octave-4.4.1-w32.zip (~ 481 MB) [signature]
Of couse a 64bit built will NOT run on a Windoze7 32bit so you have to get octave-4.4.1-w32-installer.exe and install this
I have a gateway device with MT7620a in MIPS architecture. The device has installed OpenWRT. If I connect to device via UART with the goal of flashing new firmware I see something I don't understand, MCU loading two version U-Boot.
U-Boot 1.1.3
Ralink UBoot Version: 4.3.0.0
Here is Log System after start
U-Boot 1.1.3 (Apr 27 2015 - 13:54:38)
Board: Ralink APSoC DRAM: 128 MB
relocate_code Pointer at: 87fb8000
enable ephy clock...done. rf reg 29 = 5
SSC disabled.
spi_wait_nsec: 29
spi device id: 1c 70 18 1c 70 (70181c70)
find flash: EN25QH128A
raspi_read: from:30000 len:1000
*** Warning - bad CRC, using default environment
============================================
Ralink UBoot Version: 4.3.0.0
--------------------------------------------
ASIC 7620_MP (Port5<->None)
DRAM component: 1024 Mbits DDR, width 16
DRAM bus: 16 bit
Total memory: 128 MBytes
Flash component: SPI Flash
Date:Apr 27 2015 Time:13:54:38
Of course I have a few additional questions in this issue:
What is different between these U-Boot ?
Why does my device need two versions U-Boot ?
Whether this u-boots need separate *.bin image or these is together
in one image *.bin ? In my device is only one partition for u-boot image and one partition for variables:
mtd0: 00030000 00010000 "u-boot"
mtd1: 00010000 00010000 "u-boot-env"
As Alexandre Belloni said, there is probably only one version of U-Boot on your device, it just has two different version identifiers.
The reason for this is that manufacturers often need to modify the U-Boot source code in order to get it to operate on their device, or to add features.
On your device, it looks like the version of U-Boot that Ralink pulled from the official U-Boot source code repository is 1.1.3. Ralink's own internal version number that they use for tracking their internal modifications is 4.3.0.0.
There is probably only one u-boot and "Ralink UBoot Version: 4.3.0.0" is an internal u-boot version for Ralink.
Magento DB query to large works the first time then crashes.
I have about 6000 products and I need to put my category's into alphabetical order. The first time I make a move it takes about 45 min and works. Then any after that fail. mySQL is still up and going on other sites. but if I restart mySQL then it will not start back up. I have to safe reboot twice.... wait a bit then it seems to reset and will work. how do i let it run a larger query or is there another way to move/organize the categories?
If any one can help I would appreciate it so much.
Thanks
P.s. any more info needed please ask.
Notification Type: failed
Notification: mysql failed # Mon Jul 1 13:27:34 2013. A restart was attempted automagically.
Service Check Method: [check command]
Number of Restart Attempts: 1
Service Check Raw Output:
mysql is not running
Restart Message:
Stuck on restart of mysql at /usr/local/cpanel/Cpanel/TailWatch/ChkServd.pm line 1013.
Startup Log:
Starting MySQL.... SUCCESS!
Memory Information:
Used: 348MB
Available: 3099MB
Installed: 3447MB
Load Information: 18.49 12.34 6.95
Uptime: 199 days, 16 hours, 39 seconds
IOStat Information:
avg-cpu: %user %nice %system %iowait %steal %idle
0.44 0.23 0.31 0.84 0.00 98.18
Device: tps Blk_read/s Blk_wrtn/s Blk_read Blk_wrtn
vda 30.25 103.89 151.29 1792508458 2610237768
vda1 30.25 103.89 151.29 1792508098 2610237768
vdb 0.01 0.19 0.25 3278144 4279560