Coder Social home page Coder Social logo

cess-miner's Introduction

CESS-BUCKET
GitHub license Go Reference build Go Report Card

CESS-Bucket is a mining program provided by cess platform for storage miners.

📝 Reporting a Vulnerability

If you find any system errors or you have better suggestions, please submit an issue or submit a pull request. You can also join the CESS discord to communicate with us.

📢 Announcement

CESS test network rpc endpoints

wss://testnet-rpc.cess.network/ws/

CESS test network bootstrap node

_dnsaddr.boot-miner-testnet.cess.network

🚰 CESS test network faucet

https://www.cess.network/faucet.html

⚠ Attention

The following commands are executed with root privileges, if the prompt Permission denied appears, you need to switch to root privileges, or add sudo at the top of these commands.

⚙ System configuration

System requirements

  • Linux 64-bit Intel/AMD

Install application tools

For the Debian and ubuntu families of linux systems:

# apt install git curl wget vim util-linux -y

For the Fedora, RedHat and CentOS families of linux systems:

# yum install git curl wget vim util-linux -y

Firewall configuration

By default, cess-miner uses port 4001 to listen for incoming connections, if your platform blocks these two ports by default, you may need to enable access to these port.

ufw

For hosts with ufw enabled (Debian, Ubuntu, etc.), you can use the ufw command to allow traffic to flow to specific ports. Use the following command to allow access to a port:

# ufw allow 4001

firewall-cmd

For hosts with firewall-cmd enabled (CentOS), you can use the firewall-cmd command to allow traffic on specific ports. Use the following command to allow access to a port:

# firewall-cmd --get-active-zones

This command gets the active zone(s). Now, apply port rules to the relevant zones returned above. For example if the zone is public, use

# firewall-cmd --zone=public --add-port=4001/tcp --permanent

Note that permanent makes sure the rules are persistent across firewall start, restart or reload. Finally reload the firewall for changes to take effect.

# firewall-cmd --reload

iptables

For hosts with iptables enabled (RHEL, CentOS, etc.), you can use the iptables command to enable all traffic to a specific port. Use the following command to allow access to a port:

iptables -A INPUT -p tcp --dport 4001 -j ACCEPT
service iptables restart

Network optimization (optional)

sysctl -w net.ipv4.tcp_syncookies = 1
sysctl -w net.ipv4.tcp_tw_reuse = 1
sysctl -w net.ipv4.tcp_tw_recycle = 1
sysctl -w net.ipv4.tcp_fin_timeout = 30
sysctl -w net.ipv4.tcp_max_syn_backlog = 8192
sysctl -w net.ipv4.tcp_max_tw_buckets = 6000
sysctl -w net.ipv4.tcp_timestsmps = 0
sysctl -w net.ipv4.ip_local_port_range = 10000 65500

💰 Configure CESS wallet

1) Register two cess wallet

For wallet one, it is called an earnings account, which is used to receive rewards from mining, and you should keep the private key carefully.

For wallet two, it is called a staking account and is used to staking some tokens and sign blockchain transactions.

Please refer to Create-CESS-Wallet to create your cess wallet.

2) Recharge your staking account

The staking amount is calculated based on the space you configure. The minimum staking amount is 4000CESS, and an additional 4000CESS staking is required for each additional 1TiB of space.

If you are using the test network, Please join the CESS discord to get it for free. If you are using the official network, please buy CESS tokens.

🏗 Get the binary program

Method one

Download the latest release of the binary application directly at:

# wget https://github.com/CESSProject/cess-miner/releases/download/v0.7.11/bucket0.7.11.linux-amd64.tar.gz

Method two

Compile the binary program from the storage node source code and follow the process as follows:

1) install go CESS-Bucket requires Go 1.21, See the official Golang installation instructions.

Open gomod mode:

# go env -w GO111MODULE="on"

Users in China can add go proxy to speed up the download:

# go env -w GOPROXY="https://goproxy.cn,direct"

2) clone code

# git clone https://github.com/CESSProject/cess-miner.git

3) compile code

# cd cess-miner/
# go build -o miner cmd/main.go

4) Grant execute permission

# chmod +x miner

5) View miner features (optional)

The miner has many functions, you can use ./miner -h or ./miner --help to view, as follows:

  • Flags
Flag Description
-c,--config custom configuration file (default "conf.yaml")
-h,--help help for cess-miner
--earnings earnings account
--port listening port
--rpc rpc endpoint list
--space maximum space used(GiB)
--ws workspace
  • Available Commands
Command Subcommand Description
version Print version number
config Generate configuration file
stat Query storage miner information
run Automatically register and run
exit Unregister the storage miner role
increase staking Increase the staking
increase space Increase the declaration space
withdraw Withdraw stakes
update earnings Update earnings account
reward Query reward information
claim Claim reward

🟢 Start mining

The miner program has two running modes: foreground and background.

⚠️ If you are not running the miner program with root privileges, make sure that the user you are currently logged in to has all permissions for the workspace directory you have configured. If you are logged in as user, the configured directory is /cess, and your signature account is cXfyomKDABfehLkvARFE854wgDJFMbsxwAJEHezRb6mfcAi2y, execute the following command to grant permissions:

# chown -R  user:user /cess/cXfyomKDABfehLkvARFE854wgDJFMbsxwAJEHezRb6mfcAi2y/

Foreground operation mode

The foreground operation mode requires the terminal window to be kept all the time, and the window cannot be closed. You can use the screen command to create a window for the miner and ensure that the window always exists. Create and enter the miner window command:

# screen -S miner

Press ctrl + A + D to exit the miner window without closing it.

View window list command:

# screen -ls

Re-enter the miner window command:

# screen -r miner

method one

Enter the miner run command to run directly, and enter the information according to the prompt to complete the startup:

# ./miner run
>> Please enter the rpc address of the chain, multiple addresses are separated by spaces:
wss://testnet-rpc.cess.network/ws/
>> Please enter the workspace, press enter to use / by default workspace:
/
>> Please enter your earnings account, if you are already registered and do not want to update, please press enter to skip:
cXfyomKDABfehLkvARFE854wgDJFMbsxwAJEHezRb6mfcAi2y
>> Please enter your service port:
15001
>> Please enter the maximum space used by the storage node in GiB:
2000
>> Please enter the mnemonic of the staking account:
*******************************************************************************

method two

# ./miner run --rpc wss://testnet-rpc.cess.network/ws/ --ws / --earnings cXfyomKDABfehLkvARFE854wgDJFMbsxwAJEHezRb6mfcAi2y --port 4001 --space 2000
>> Please enter the mnemonic of the staking account:
*******************************************************************************

Background operation mode

Generate configuration file:

# ./miner config
OK /root/miner/conf.yaml

Edit the configuration file and fill in the correct information, then run:

# nohup ./miner run -c /root/miner/conf.yaml &

If the configuration file is named conf.yaml and is located in the same directory as the miner program, you can specify without -c:

# nohup ./miner run &

💡 Other commands

  • stat
# ./miner stat --rpc wss://testnet-rpc.cess.network/ws/
>> Please enter the mnemonic of the staking account:
*******************************************************************************
+-------------------+------------------------------------------------------+
| name              | storage miner                                        |
| peer id           | 12D3KooWSEX3UkyU2R6S1wERs4iH7yp2yVCWX2YkReaokvCg7uxU |
| state             | positive                                             |
| staking amount    | 2400 TCESS                                           |
| staking start     | 3123                                                 |
| debt amount       | 0 TCESS                                              |
| declaration space | 1.00 TiB                                             |
| validated space   | 1.00 GiB                                             |
| used space        | 25.00 MiB                                            |
| locked space      | 0 bytes                                              |
| signature account | cXgDBpxj2vHhR9qP8wTkZ5ZST9YMu6WznFsEAZi3SZPD4b4qw    |
| staking account   | cXgDBpxj2vHhR9qP8wTkZ5ZST9YMu6WznFsEAZi3SZPD4b4qw    |
| earnings account  | cXjeCHQW3totBGhQXdAUAqjCNqk1NhiR3UK37czSeUak2pqGV    |
+-------------------+------------------------------------------------------+
  • increase staking
# ./miner increase staking 1000000000000000000000 --rpc wss://testnet-rpc.cess.network/ws/
>> Please enter the mnemonic of the staking account:
*******************************************************************************
OK 0xe098179a4a668690f28947d20083014e5a510b8907aac918e7b96efe1845e053
  • increase space
# ./miner increase space 10 --rpc wss://testnet-rpc.cess.network/ws/
>> Please enter the mnemonic of the staking account:
*******************************************************************************
OK 0xe098179a4a668690f28947d20083014e5a510b8907aac918e7b96efe1845e053
  • update earnings
# ./miner update earnings cXgDBpxj2vHhR9qP8wTkZ5ZST9YMu6WznFsEAZi3SZPD4b4qw --rpc wss://testnet-rpc.cess.network/ws/
>> Please enter the mnemonic of the staking account:
*******************************************************************************
OK 0x0fa67b89d9f8ff134b45e4e507ccda00c0923d43c3b8166a2d75d3f42e5a269a
  • version
./miner version
miner v0.7.11
  • exit
# ./miner exit --rpc wss://testnet-rpc.cess.network/ws/
>> Please enter the mnemonic of the staking account:
*******************************************************************************
OK 0xf6e9573ba53a90c4bbd8c3784ef97bbf74bdb1cf8c01df697310a64c2a7d4513
  • withdraw
# ./miner withdraw --rpc wss://testnet-rpc.cess.network/ws/
>> Please enter the mnemonic of the staking account:
*******************************************************************************
OK 0xfbcc77c072f88668a83f2dd3ea00f3ba2e5806aae8265cfba1582346d6ada3f1
  • claim
# ./miner claim --rpc wss://testnet-rpc.cess.network/ws/
>> Please enter the mnemonic of the staking account:
*******************************************************************************
OK 0x59096fd095b66665c838f89ae4f1384ab31255cdc9c80003b05b50124cfdcfee
  • reward
# ./miner reward --rpc wss://testnet-rpc.cess.network/ws/
>> Please enter the mnemonic of the staking account:
*******************************************************************************
+------------------+---------------------------+
| total reward     | 2_613_109_650_924_024_640 |
| claimed reward   | 534_235_750_855_578_370   |
| unclaimed reward | 0                         |
+------------------+---------------------------+

License

Licensed under Apache 2.0

cess-miner's People

Contributors

0xbillw avatar aranck avatar astafrode avatar daichibret avatar jiuquxzy avatar swowk avatar tehsunnliu avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

cess-miner's Issues

Consensus node configuration issues

Hello team,

I am trying to configure a consensus node. following this tutorial (https://docs.cess.cloud/core/consensus-miner/running). Everything goes smoothly up until I try to generate the session key.
When typing the command "cess tools rotate-keys" I get "null" as an output. I have tried many times and checked everything more than once. Asked questions in the discord channel and presented info there but no one was able to help so far.
The next screenshots are after I did "cess down"; "cess purge"; "cess config set"; "cess start" and "cess tools rotate-keys".

Screenshot 2024-01-16 191504

Screenshot 2024-01-16 233422

Screenshot 2024-01-16 233648

Can someone help?

cess config set 这步不填IP,结束配置内容后又提示是什么操作

cess config set 时,没让输入IP啊,配置完成时提示Set configurations successfully,接着就提示Start generate configurations and docker compose file
debug: Loading config file: config.yaml
error: failed to load config: '"node.externalIp" is not allowed to be empty'
Trace: [Error [ValidationError]: "node.externalIp" is not allowed to be empty] {
这里提示没有IP,这不是前后矛盾吗?

Validated space not increase in 3 weeks

I installed as a storage miner, but 3 weeks have passed, my validated space has not increased at all, even though I updated to the latest version 0.4.4.
Please check it for me and give me feedback.

image

Cannot increase staking amount

I setup CESS v0.5.3 okay, after setup, I see have many error on chain log:

docker logs -f chain

2024-01-31 14:32:08 Report 12D3KooWBAfrmibBjSosGKZvV8PKavTPQcZ2heUYEs1k5CPgBn3k: -2147483648 to -2147483648. Reason: Genesis mismatch. Banned, disconnecting. 2024-01-31 14:32:08 💤 Idle (45 peers), best: #2049 (0xd0ba…0ac4), finalized #2046 (0xc042…592b), ⬇ 12.9kiB/s ⬆ 17.5kiB/s 2024-01-31 14:32:09 Report 12D3KooWMyVXx5S8zpZy2HNErDSEp2kmZswuv6HtLCmqbYxK2K9H: -2147483648 to -2147483648. Reason: Genesis mismatch. Banned, disconnecting. 2024-01-31 14:32:09 Report 12D3KooWFvMy6z2CcNYmWYMFe5Hp1hyH4FxuhZCGk9iubtd2CwD3: -2147483648 to -2147483648. Reason: Genesis mismatch. Banned, disconnecting. 2024-01-31 14:32:09 Report 12D3KooWDMEaCDzebaLKkbyc2whETN8GiVRsdhCaJByynpVp6ghf: -2147483648 to -2147483648. Reason: Genesis mismatch. Banned, disconnecting. 2024-01-31 14:32:09 Report 12D3KooWQKS8KWFUAZxLaiBWW9MoPMJYupinE4DZkqixcPDntzAi: -2147483648 to -2147483648. Reason: Genesis mismatch. Banned, disconnecting. 2024-01-31 14:32:09 Report 12D3KooWLjh3KJnD9xjeC8T6s95U4r5kegUH9fH9wGLsFpgbBMB5: -2147483648 to -2147483648. Reason: Genesis mismatch. Banned, disconnecting. 2024-01-31 14:32:10 Report 12D3KooWKf1VxRmLJor1s3aTrLYd4Tife3Q3WLgaQBeKqhEWfuxf: -2147483648 to -2147483648. Reason: Genesis mismatch. Banned, disconnecting. 2024-01-31 14:32:10 Report 12D3KooWQHFjt3fxTK2Z9qTBs2YbwiCUzHHnDvgNGUt34o4HsFaL: -2147483648 to -2147483648. Reason: Genesis mismatch. Banned, disconnecting. 2024-01-31 14:32:11 Report 12D3KooWEUR8KxceqtHqoqhiWEQkyRiE5Tm45byApT2R2WxxYb7b: -2147483648 to -2147483648. Reason: Genesis mismatch. Banned, disconnecting. 2024-01-31 14:32:12 ✨ Imported #2050 (0x15c6…5d36) 2024-01-31 14:32:12 ♻️ Reorg on #2050,0x15c6…5d36 to #2050,0x933c…6623, common ancestor #2049,0xd0ba…0ac4 2024-01-31 14:32:12 ✨ Imported #2050 (0x933c…6623) 2024-01-31 14:32:12 Report 12D3KooWMwkt6NSxLrSoFnYENhzwm9q9nPXghVbFsngByHQv3eAK: -2147483648 to -2147483648. Reason: Genesis mismatch. Banned, disconnecting.

And bucket stat got frozen status:

cess bucket stat

XX 2024-01-31 14:32:52 your staking starting block is not found +-------------------+------------------------------------------------------+ | name | storage miner | | peer id | 12D3KooWRHG6uBcmADD45FZTMZ5NBFXXD9vaeC3iU4usAjd9b9vA | | state | frozen | | staking amount | 0 TCESS | | staking start | 0 | | debt amount | 0 TCESS | | declaration space | 2.00 TiB | | validated space | 0 Bytes | | used space | 0 Bytes | | locked space | 0 Bytes | | signature account | cXjshkdUTGasVhgBGRqdkRxxxxxxxxxxxxAt2frGSaXQrTnNUbb | | staking account | cXjshkdUTGasVhgBGRqdkRVWsGFxxxxxxxxxxxxxxxxxxxnNUbb | | earnings account | cXiupjLvU75QBLzNkqZjeS5Pzqxxxxxxxxxxx5opcBLNqvKYXEro | +-------------------+------------------------------------------------------+

and I also cannot increment staking amount to avoid frozen state:

root@cess:~/cess-nodeadm# cess bucket increase staking 9000 XX 2024-01-31 14:34:32 Please enter the correct staking amount

Notice: I already faucet to staking account.

Please help me check,
Thank you

Ceseal Container keep restating

My node keep crasing and entering this looping :

EBUG RS - deno_runtime::permissions:86 - ⚠️️  Granted read access to "/opt/ceseal/releases/24013112/data/protected_files/runtime-data.seal"
runtime-data.seal exists, no need to handover
Work dir '/opt/ceseal/releases/24013112'
Data dir '/opt/ceseal/releases/24013112/data'
Starting Ceseal with extra opts '--role=full '
Ceseal will running in hardware mode
Gramine is starting. Parsing TOML manifest file, this may take some time...
-----------------------------------------------------------------------------------------------------------------------
Gramine detected the following insecure configurations:

  - loader.insecure__use_cmdline_argv = true   (forwarding command-line args from untrusted host to the app)
  - sys.insecure__allow_eventfd = true         (host-based eventfd is enabled)
  - sgx.allowed_files = [ ... ]                (some files are passed through from untrusted host without verification)

Gramine will continue application execution, but this configuration must not be used in production!
-----------------------------------------------------------------------------------------------------------------------

Running in Gramine-SGX
mr_enclave  : 0x9b97f27980336c73a43719e9f53092051ee7d4df281390b2e9d7451a8b8f8e2a
mr_signer   : 0x8ab66057ac1cbbd49fa645d937008f550c5bd355af21dbea7a73d589df738265
isv_svn     : 0x0000
isv_prod_id : 0x0000
git revision: 55dff8c
2024-02-04T16:41:56.871103Z  INFO main: ceseal: Starting ceseal... sgx=true
2024-02-04T16:41:56.871149Z  INFO main: ceseal: cores=16
2024-02-04T16:41:56.871161Z  INFO main: ceseal: init_args: InitArgs {
    sealing_path: "/data/protected_files",
    storage_path: "/data/storage_files",
    version: "0.1.0",
    git_revision: "55dff8c-2024-01-31T12:48:46.117109259Z",
    enable_checkpoint: true,
    checkpoint_interval: 900,
    remove_corrupted_checkpoint: false,
    max_checkpoint_files: 5,
    cores: 16,
    public_port: None,
    safe_mode_level: 0,
    no_rcu: false,
    ra_timeout: 8s,
    ra_max_retries: 1,
    role: Full,
}
2024-02-04T16:41:56.871904Z  INFO main: cestory: Loading checkpoint from file "/data/storage_files/checkpoint.seal-000037141"
2024-02-04T16:41:58.367709Z  INFO main: cestory: Succeeded to load checkpoint file "/data/storage_files/checkpoint.seal-000037141"
2024-02-04T16:41:58.367751Z  INFO main: cestory: Loaded checkpoint
2024-02-04T16:41:58.367762Z  INFO main: cestory: keyfairy is ready by restore
2024-02-04T16:41:58.367911Z  INFO main: cestory: Enclave init OK
2024-02-04T16:41:58.368250Z  INFO cestory: Ceseal internal server will listening on 0.0.0.0:8000
2024-02-04T16:42:01.370553Z DEBUG cestory: Successfully load podr2 key public key is: [48, 130, 1, 10, 2, 130, 1, 1, 0, 178, 57, 227, 166, 30, 237, 82, 178, 235, 233, 170, 96, 37, 140, 170, 182, 135, 66, 188, 24, 189, 190, 149, 75, 125, 94, 230, 1, 154, 122, 80, 226, 15, 190, 6, 192, 61, 114, 197, 53, 116, 64, 156, 224, 226, 128, 169, 128, 95, 145, 109, 102, 52, 148, 190, 12, 71, 175, 101, 91, 66, 188, 9, 166, 173, 225, 22, 114, 98, 31, 144, 8, 175, 29, 165, 171, 189, 126, 33, 97, 184, 52, 69, 163, 231, 126, 205, 17, 210, 34, 97, 218, 144, 82, 164, 20, 164, 215, 20, 181, 180, 37, 179, 99, 108, 177, 125, 70, 7, 217, 206, 103, 78, 11, 146, 150, 198, 230, 166, 221, 25, 118, 8, 187, 143, 18, 223, 78, 83, 206, 178, 39, 110, 240, 123, 5, 107, 181, 31, 125, 210, 29, 191, 238, 173, 211, 194, 243, 239, 74, 31, 241, 71, 29, 148, 100, 118, 134, 169, 132, 183, 231, 139, 200, 189, 3, 77, 234, 118, 165, 223, 164, 199, 26, 176, 236, 165, 7, 232, 102, 197, 161, 59, 217, 1, 183, 177, 64, 60, 132, 6, 234, 226, 60, 157, 133, 219, 115, 213, 18, 145, 86, 229, 123, 189, 113, 147, 196, 180, 217, 15, 179, 109, 161, 255, 60, 202, 94, 228, 98, 209, 13, 19, 205, 40, 161, 189, 169, 190, 211, 217, 150, 67, 180, 242, 60, 173, 223, 209, 166, 4, 221, 206, 238, 96, 147, 199, 225, 203, 200, 241, 247, 225, 54, 20, 161, 2, 3, 1, 0, 1]
error: There are no available TCS pages left for a new thread. Please try to increase sgx.max_threads in the manifest. The current value is 128
[P1:T2:ceseal] error: PalStreamOpen failed: Operation denied (PAL_ERROR_DENIED)
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 11, kind: WouldBlock, message: "Resource temporarily unavailable" }', /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/threadpool-1.8.1/src/lib.rs:777:10
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
error: There are no available TCS pages left for a new thread. Please try to increase sgx.max_threads in the manifest. The current value is 128
[P1:T125:ceseal] error: PalStreamOpen failed: Operation denied (PAL_ERROR_DENIED)
[P1:T125:ceseal] error: failed to set up async cleanup_thread (exiting without clear child tid), return code: Cannot allocate memory (ENOMEM)
error: There are no available TCS pages left for a new thread. Please try to increase sgx.max_threads in the manifest. The current value is 128
[P1:T97:ceseal] error: PalStreamOpen failed: Operation denied (PAL_ERROR_DENIED)
[P1:T97:ceseal] error: failed to set up async cleanup_thread (exiting without clear child tid), return code: Cannot allocate memory (ENOMEM)
error: Host injected malicious signal 2
ceseal exited with code 1

kld-sgx resets every 35 secs

Hello!
I updated my consensus node to 0.4.2, but kld-sgx resets every 35 secs
image
my CESS account is cXfCo1Md28eweWfBuhJeXvECz2aUTjq3MLxFWigHH96oWoi71
I tried to reinstall from a scratch. It didn't help
SGX and FLC are supported by CPU
image

rpc issues

i have been having rpc connection issues for the past three days even after doing a restart on two occasions.
Uploading Screenshot 2024-01-24 102029.png…

mining reward question

when i cancel the cess mining system, the tips show i should keep the mining machine running and get the staking back on 30 days. but the question is my mining machine was shut down already, can i get my staking and mining reward back ?

How to revive punished to 0 node?

one of my nodes got punished to 0 and node went offline. I do faucet and have tokens on my wallet, but can't revive it. What can I do with it?
cess bucket increase doesn't work
bucket can't start. I tried everything I know. I need help
image

image

配置挖矿操作问题

1.注册矿工时meat mask钱包会合约交互失败导致无法注册矿工
2.挖矿miner配置时将钱包中的私钥已经写入priv文件却使用geth account import ./priv生成keystore文件时出现找不到私钥的错误
屏幕截图 2022-04-20 040658

[Init Pois-2] errors again

I have that issue again
image

chain looks good
image

cess bucket stat looks good too
image

do I need to do something to fix it? Last time I created new wallet to fix it. But I think that's not a good option.

Can't start consensu node with SGX2

cpuid -1 | grep SGX
      SGX: Software Guard Extensions supported = true
      SGX_LC: SGX launch config supported      = true
   Software Guard Extensions (SGX) capability (0x12/0):
      SGX1 supported                           = true
      SGX2 supported                           = true
      SGX ENCLV E*VIRTCHILD, ESETCONTEXT       = true
      SGX ENCLS ETRACKC, ERDINFO, ELDBC, ELDUC = true
   SGX attributes: ECREATE SECS.ATTRIBUTES (0x12/1):
   SGX Enclave Page Cache (EPC) enumeration (0x12/0x2):
   SGX Enclave Page Cache (EPC) enumeration (0x12/0x3):
Screenshot 2024-02-04 at 00 36 11

log of ceseal container :

EBUG RS - deno_runtime::permissions:86 - ⚠️️  Granted net access to "deno.land"
DEBUG RS - deno::file_fetcher:254 - FileFetcher::fetch_cached - specifier: https://deno.land/[email protected]/path/_common/glob_to_reg_exp.ts
DEBUG RS - deno::file_fetcher:550 - FileFetcher::fetch() - specifier: https://deno.land/[email protected]/path/posix/_util.ts
DEBUG RS - deno_runtime::permissions:86 - ⚠️️  Granted net access to "deno.land"
DEBUG RS - deno::file_fetcher:344 - FileFetcher::fetch_remote() - specifier: https://deno.land/[email protected]/path/posix/_util.ts
DEBUG RS - deno_runtime::permissions:86 - ⚠️️  Granted net access to "deno.land"
DEBUG RS - deno::file_fetcher:254 - FileFetcher::fetch_cached - specifier: https://deno.land/[email protected]/path/posix/_util.ts
DEBUG RS - deno::npm::managed::resolution:313 - Snapshot already up to date. Skipping pending resolution.
DEBUG RS - deno::module_loader:218 - Prepared module load.
DEBUG RS - deno_runtime::permissions:86 - ⚠️️  Granted read access to "/opt/ceseal/releases/current"
Current /opt/ceseal/releases/24013112
DEBUG RS - deno_runtime::permissions:86 - ⚠️️  Granted read access to "/opt/ceseal/releases/24013112/data/protected_files/runtime-data.seal"
DEBUG RS - deno_runtime::permissions:86 - ⚠️️  Granted read access to "/opt/ceseal/backups"
No previous version, no need to handover!
DEBUG RS - deno_runtime::permissions:86 - ⚠️️  Granted read access to "/opt/ceseal/releases/24013112"
DEBUG RS - deno_runtime::permissions:86 - ⚠️️  Granted read access to "/opt/ceseal/backups/24013112"
'/opt/ceseal/backups/24013112' already exists.
Work dir '/opt/ceseal/releases/24013112'
Data dir '/opt/ceseal/releases/24013112/data'
Starting Ceseal with extra opts '--role=full '
Ceseal will running in hardware mode
Gramine is starting. Parsing TOML manifest file, this may take some time...
error: AESM service returned error 31; this may indicate that infrastructure for the EPID attestation requested by Gramine is missing on this machine
error: load_enclave() failed with error: Operation not permitted (EPERM)
ceseal exited with code 255

Account hacked

I bought 10 cess with 0.5eth
My wallet was compromised and the hacker attached a sweeper bot. Is there a way to change my wallet? The address I contributed was 0x43bEAAf55b402A7b59b8d2696eC040Fd09f6c001

About RPC errors

When I run "docker logs bucket",

rpc err: [ws://127.0.0.1:9944] [st] [Sminer.Expenders] CreateStorageKey: module Sminer not found in metadata

2024-02-11 143351

I get the above error.

I added "wss://testnet-rpc2.cess.cloud/ws/" to config.yaml but it does not improve.

Is there any way to deal with this?

websocket: bad handshake

Hi Team, may be there is a problem with RPC or port somewhere:
websocket: bad handshake (HTTP status 429 Too Many Requests)

3 nodes of 4 is not getting storage verified

three nodes of four does not get storage verified for 4 days already. There is no errors in logs
staking addresses are
cXhxtHBSk5yicDbeoGFKNdgptidGeQgjMe4Am2XJjdmfup8E7
cXiP9A1xRuGkU8dnr3qBWp5T7BqJcbAfzVpqGm7NYnHpAQL1q
cXgencksSUsosSUYf6iQwZgKyQPVYSjxRS2b36mX7fDZmooFv

I have 4th node which has similar technical characteristics but it gets storage verified
staking address is
cXgqNFFxw15Q6uvFwbuCZNkoFEotnhwmiegvjg7Zm7xqyocBy

image
please help

cess-bucket spamming internal servers

I've received a report from my hosting provider that some process from port 15001 attacks internal servers. Report bellow.
Please fix it ASAP

##########################################################################

Netscan detected from host 65.109.103.215

##########################################################################

time protocol src_ip src_port dest_ip dest_port

Sun Sep 3 09:54:44 2023 TCP 65.109.103.215 15001 => 192.168.7.95 15005
Sun Sep 3 10:03:10 2023 TCP 65.109.103.215 15001 => 192.168.7.95 15005
Sun Sep 3 09:57:59 2023 TCP 65.109.103.215 15001 => 192.168.1.2 62316
Sun Sep 3 09:59:26 2023 TCP 65.109.103.215 15001 => 192.168.1.2 62316
Sun Sep 3 10:02:35 2023 TCP 65.109.103.215 15001 => 192.168.1.2 62316
Sun Sep 3 10:02:37 2023 TCP 65.109.103.215 15001 => 192.168.1.2 62316
Sun Sep 3 09:55:52 2023 TCP 65.109.103.215 15001 => 10.9.11.7 6706
Sun Sep 3 09:55:53 2023 TCP 65.109.103.215 15001 => 10.9.11.7 6706
Sun Sep 3 09:58:59 2023 TCP 65.109.103.215 15001 => 192.168.31.185 18005
Sun Sep 3 09:59:00 2023 TCP 65.109.103.215 15001 => 192.168.31.185 18005
Sun Sep 3 09:59:25 2023 TCP 65.109.103.215 15001 => 10.99.76.6 40005
Sun Sep 3 10:00:13 2023 TCP 65.109.103.215 15001 => 10.99.76.6 40005
Sun Sep 3 10:03:05 2023 TCP 65.109.103.215 15001 => 10.99.76.6 40005
Sun Sep 3 10:00:53 2023 TCP 65.109.103.215 15001 => 10.42.22.23 51002
Sun Sep 3 10:00:55 2023 TCP 65.109.103.215 15001 => 10.42.22.23 51002
Sun Sep 3 09:56:38 2023 TCP 65.109.103.215 15001 => 10.42.23.24 51002
Sun Sep 3 09:58:43 2023 TCP 65.109.103.215 15001 => 10.42.23.24 51002
Sun Sep 3 09:56:45 2023 TCP 65.109.103.215 15001 => 10.42.28.22 51002
Sun Sep 3 09:56:46 2023 TCP 65.109.103.215 15001 => 10.42.28.22 51002
Sun Sep 3 09:58:41 2023 TCP 65.109.103.215 15001 => 10.42.28.22 51002
Sun Sep 3 09:58:59 2023 TCP 65.109.103.215 15001 => 10.42.31.22 51002
Sun Sep 3 10:02:07 2023 TCP 65.109.103.215 15001 => 10.42.32.22 51002
Sun Sep 3 10:01:48 2023 TCP 65.109.103.215 15001 => 10.42.37.26 51002
Sun Sep 3 10:02:09 2023 TCP 65.109.103.215 15001 => 10.42.39.24 51002
Sun Sep 3 10:03:38 2023 TCP 65.109.103.215 15001 => 10.42.41.32 51002
Sun Sep 3 10:03:23 2023 TCP 65.109.103.215 15001 => 10.42.42.24 51002
Sun Sep 3 10:03:24 2023 TCP 65.109.103.215 15001 => 10.42.42.24 51002
Sun Sep 3 10:03:26 2023 TCP 65.109.103.215 15001 => 10.42.42.24 51002
Sun Sep 3 09:56:40 2023 TCP 65.109.103.215 15001 => 10.42.50.28 51002
Sun Sep 3 09:56:43 2023 TCP 65.109.103.215 15001 => 10.42.50.28 51002
Sun Sep 3 09:58:38 2023 TCP 65.109.103.215 15001 => 10.42.50.28 51002
Sun Sep 3 09:57:21 2023 TCP 65.109.103.215 15001 => 10.42.51.22 51002
Sun Sep 3 09:57:22 2023 TCP 65.109.103.215 15001 => 10.42.51.22 51002
Sun Sep 3 10:02:02 2023 TCP 65.109.103.215 15001 => 10.42.56.45 51002
Sun Sep 3 10:02:03 2023 TCP 65.109.103.215 15001 => 10.42.56.45 51002
Sun Sep 3 09:57:28 2023 TCP 65.109.103.215 15001 => 10.42.60.14 51002
Sun Sep 3 09:57:30 2023 TCP 65.109.103.215 15001 => 10.42.60.14 51002
Sun Sep 3 10:00:31 2023 TCP 65.109.103.215 15001 => 10.100.97.95 40034
Sun Sep 3 09:59:06 2023 TCP 65.109.103.215 15001 => 10.100.97.127 40017
Sun Sep 3 10:03:04 2023 TCP 65.109.103.215 15001 => 10.111.40.242 40040
Sun Sep 3 09:58:47 2023 TCP 65.109.103.215 15001 => 10.100.97.68 40015
Sun Sep 3 09:59:00 2023 TCP 65.109.103.215 15001 => 10.42.24.24 51003
Sun Sep 3 09:59:02 2023 TCP 65.109.103.215 15001 => 10.42.24.24 51003
Sun Sep 3 10:00:47 2023 TCP 65.109.103.215 15001 => 10.42.28.25 51003
Sun Sep 3 10:00:52 2023 TCP 65.109.103.215 15001 => 10.42.29.25 51003
Sun Sep 3 10:00:53 2023 TCP 65.109.103.215 15001 => 10.42.29.25 51003
Sun Sep 3 10:00:55 2023 TCP 65.109.103.215 15001 => 10.42.29.25 51003
Sun Sep 3 09:55:24 2023 TCP 65.109.103.215 15001 => 10.42.30.37 51003
Sun Sep 3 10:02:07 2023 TCP 65.109.103.215 15001 => 10.42.33.25 51003
Sun Sep 3 10:02:09 2023 TCP 65.109.103.215 15001 => 10.42.33.25 51003
Sun Sep 3 10:02:11 2023 TCP 65.109.103.215 15001 => 10.42.33.25 51003
Sun Sep 3 10:03:29 2023 TCP 65.109.103.215 15001 => 10.42.36.23 51003
Sun Sep 3 10:03:31 2023 TCP 65.109.103.215 15001 => 10.42.36.23 51003
Sun Sep 3 10:03:35 2023 TCP 65.109.103.215 15001 => 10.42.36.23 51003
Sun Sep 3 09:59:06 2023 TCP 65.109.103.215 15001 => 10.42.37.25 51003
Sun Sep 3 09:59:11 2023 TCP 65.109.103.215 15001 => 10.42.37.25 51003
Sun Sep 3 10:00:33 2023 TCP 65.109.103.215 15001 => 10.42.37.25 51003
Sun Sep 3 10:00:19 2023 TCP 65.109.103.215 15001 => 10.42.38.24 51003
Sun Sep 3 10:00:21 2023 TCP 65.109.103.215 15001 => 10.42.38.24 51003
Sun Sep 3 10:01:54 2023 TCP 65.109.103.215 15001 => 10.42.38.24 51003
Sun Sep 3 10:01:55 2023 TCP 65.109.103.215 15001 => 10.42.38.24 51003
Sun Sep 3 09:55:17 2023 TCP 65.109.103.215 15001 => 10.42.40.28 51003
Sun Sep 3 09:58:14 2023 TCP 65.109.103.215 15001 => 10.42.40.28 51003
Sun Sep 3 09:59:36 2023 TCP 65.109.103.215 15001 => 10.42.40.28 51003
Sun Sep 3 09:59:38 2023 TCP 65.109.103.215 15001 => 10.42.40.28 51003
Sun Sep 3 09:59:51 2023 TCP 65.109.103.215 15001 => 10.42.40.28 51003
Sun Sep 3 09:59:54 2023 TCP 65.109.103.215 15001 => 10.42.40.28 51003
Sun Sep 3 10:03:07 2023 TCP 65.109.103.215 15001 => 10.42.40.28 51003
Sun Sep 3 10:03:08 2023 TCP 65.109.103.215 15001 => 10.42.40.28 51003
Sun Sep 3 09:55:52 2023 TCP 65.109.103.215 15001 => 10.42.41.33 51003
Sun Sep 3 09:56:43 2023 TCP 65.109.103.215 15001 => 10.42.42.25 51003
Sun Sep 3 09:56:45 2023 TCP 65.109.103.215 15001 => 10.42.42.25 51003
Sun Sep 3 09:59:26 2023 TCP 65.109.103.215 15001 => 10.42.43.30 51003
Sun Sep 3 09:59:27 2023 TCP 65.109.103.215 15001 => 10.42.43.30 51003
Sun Sep 3 09:59:29 2023 TCP 65.109.103.215 15001 => 10.42.43.30 51003
Sun Sep 3 10:00:58 2023 TCP 65.109.103.215 15001 => 10.42.43.30 51003
Sun Sep 3 10:02:33 2023 TCP 65.109.103.215 15001 => 10.42.43.30 51003
Sun Sep 3 09:56:45 2023 TCP 65.109.103.215 15001 => 10.42.44.25 51003
Sun Sep 3 09:56:45 2023 TCP 65.109.103.215 15001 => 10.42.44.25 51003
Sun Sep 3 09:56:46 2023 TCP 65.109.103.215 15001 => 10.42.44.25 51003
Sun Sep 3 09:58:36 2023 TCP 65.109.103.215 15001 => 10.42.44.25 51003
Sun Sep 3 09:58:37 2023 TCP 65.109.103.215 15001 => 10.42.44.25 51003
Sun Sep 3 09:58:39 2023 TCP 65.109.103.215 15001 => 10.42.44.25 51003
Sun Sep 3 09:57:12 2023 TCP 65.109.103.215 15001 => 10.42.49.29 51003
Sun Sep 3 09:57:14 2023 TCP 65.109.103.215 15001 => 10.42.49.29 51003
Sun Sep 3 09:59:17 2023 TCP 65.109.103.215 15001 => 10.42.51.25 51003
Sun Sep 3 09:59:18 2023 TCP 65.109.103.215 15001 => 10.42.51.25 51003
Sun Sep 3 09:59:21 2023 TCP 65.109.103.215 15001 => 10.42.51.25 51003
Sun Sep 3 10:02:19 2023 TCP 65.109.103.215 15001 => 10.42.51.25 51003
Sun Sep 3 10:02:22 2023 TCP 65.109.103.215 15001 => 10.42.51.25 51003
Sun Sep 3 09:57:17 2023 TCP 65.109.103.215 15001 => 10.42.59.14 51003
Sun Sep 3 09:57:28 2023 TCP 65.109.103.215 15001 => 10.42.60.15 51003
Sun Sep 3 09:53:46 2023 TCP 65.109.103.215 15001 => 10.111.40.240 40042
Sun Sep 3 10:02:35 2023 TCP 65.109.103.215 15001 => 10.111.40.240 40042
Sun Sep 3 10:00:09 2023 TCP 65.109.103.215 15001 => 10.0.7.56 15001
Sun Sep 3 09:56:25 2023 TCP 65.109.103.215 15001 => 10.9.11.7 15001
Sun Sep 3 09:56:28 2023 TCP 65.109.103.215 15001 => 10.9.11.7 15001
Sun Sep 3 10:01:36 2023 TCP 65.109.103.215 15001 => 10.9.11.7 15001
Sun Sep 3 10:01:37 2023 TCP 65.109.103.215 15001 => 10.9.11.7 15001
Sun Sep 3 10:01:39 2023 TCP 65.109.103.215 15001 => 10.9.11.7 15001
Sun Sep 3 09:57:10 2023 TCP 65.109.103.215 15001 => 10.15.27.203 15001
Sun Sep 3 09:57:13 2023 TCP 65.109.103.215 15001 => 10.15.27.203 15001
Sun Sep 3 09:58:54 2023 TCP 65.109.103.215 15001 => 10.15.27.211 15001
Sun Sep 3 10:03:37 2023 TCP 65.109.103.215 15001 => 10.15.27.211 15001
Sun Sep 3 10:01:46 2023 TCP 65.109.103.215 15001 => 10.15.27.231 15001
Sun Sep 3 10:01:47 2023 TCP 65.109.103.215 15001 => 10.15.27.231 15001
Sun Sep 3 09:57:09 2023 TCP 65.109.103.215 15001 => 10.15.27.233 15001
Sun Sep 3 09:58:04 2023 TCP 65.109.103.215 15001 => 10.15.27.233 15001
Sun Sep 3 09:59:25 2023 TCP 65.109.103.215 15001 => 10.15.27.233 15001
Sun Sep 3 09:59:28 2023 TCP 65.109.103.215 15001 => 10.15.27.233 15001
Sun Sep 3 10:02:33 2023 TCP 65.109.103.215 15001 => 10.15.27.233 15001
Sun Sep 3 10:02:35 2023 TCP 65.109.103.215 15001 => 10.15.27.233 15001
Sun Sep 3 09:58:55 2023 TCP 65.109.103.215 15001 => 10.30.60.13 15001
Sun Sep 3 09:58:56 2023 TCP 65.109.103.215 15001 => 10.30.60.13 15001
Sun Sep 3 10:00:40 2023 TCP 65.109.103.215 15001 => 10.30.60.13 15001
Sun Sep 3 09:56:41 2023 TCP 65.109.103.215 15001 => 10.30.60.15 15001
Sun Sep 3 09:56:45 2023 TCP 65.109.103.215 15001 => 10.30.60.15 15001
Sun Sep 3 09:58:36 2023 TCP 65.109.103.215 15001 => 10.30.60.15 15001
Sun Sep 3 09:58:37 2023 TCP 65.109.103.215 15001 => 10.30.60.15 15001
Sun Sep 3 09:58:39 2023 TCP 65.109.103.215 15001 => 10.30.60.15 15001
Sun Sep 3 09:56:39 2023 TCP 65.109.103.215 15001 => 10.30.60.17 15001
Sun Sep 3 09:58:43 2023 TCP 65.109.103.215 15001 => 10.30.60.17 15001
Sun Sep 3 09:58:46 2023 TCP 65.109.103.215 15001 => 10.30.60.17 15001
Sun Sep 3 10:03:35 2023 TCP 65.109.103.215 15001 => 10.30.60.17 15001
Sun Sep 3 09:58:53 2023 TCP 65.109.103.215 15001 => 10.30.60.18 15001
Sun Sep 3 09:58:54 2023 TCP 65.109.103.215 15001 => 10.30.60.18 15001
Sun Sep 3 09:56:38 2023 TCP 65.109.103.215 15001 => 10.30.60.19 15001
Sun Sep 3 09:58:44 2023 TCP 65.109.103.215 15001 => 10.30.60.19 15001
Sun Sep 3 09:57:38 2023 TCP 65.109.103.215 15001 => 10.30.60.21 15001
Sun Sep 3 09:57:40 2023 TCP 65.109.103.215 15001 => 10.30.60.21 15001
Sun Sep 3 10:02:01 2023 TCP 65.109.103.215 15001 => 10.30.60.21 15001
Sun Sep 3 09:55:13 2023 TCP 65.109.103.215 15001 => 10.30.60.24 15001
Sun Sep 3 10:03:37 2023 TCP 65.109.103.215 15001 => 10.30.60.25 15001
Sun Sep 3 10:00:42 2023 TCP 65.109.103.215 15001 => 10.30.60.26 15001
Sun Sep 3 09:57:47 2023 TCP 65.109.103.215 15001 => 10.30.60.27 15001
Sun Sep 3 09:57:49 2023 TCP 65.109.103.215 15001 => 10.30.60.27 15001
Sun Sep 3 09:59:00 2023 TCP 65.109.103.215 15001 => 10.30.60.31 15001
Sun Sep 3 10:00:36 2023 TCP 65.109.103.215 15001 => 10.30.60.31 15001
Sun Sep 3 09:54:08 2023 TCP 65.109.103.215 15001 => 10.30.60.33 15001
Sun Sep 3 09:55:32 2023 TCP 65.109.103.215 15001 => 10.30.60.33 15001
Sun Sep 3 09:56:21 2023 TCP 65.109.103.215 15001 => 10.30.60.33 15001
Sun Sep 3 09:56:51 2023 TCP 65.109.103.215 15001 => 10.30.60.33 15001
Sun Sep 3 09:58:21 2023 TCP 65.109.103.215 15001 => 10.30.60.33 15001
Sun Sep 3 09:59:41 2023 TCP 65.109.103.215 15001 => 10.30.60.33 15001
Sun Sep 3 09:59:42 2023 TCP 65.109.103.215 15001 => 10.30.60.33 15001
Sun Sep 3 09:59:44 2023 TCP 65.109.103.215 15001 => 10.30.60.33 15001
Sun Sep 3 10:00:07 2023 TCP 65.109.103.215 15001 => 10.30.60.33 15001
Sun Sep 3 10:01:10 2023 TCP 65.109.103.215 15001 => 10.30.60.33 15001
Sun Sep 3 10:01:11 2023 TCP 65.109.103.215 15001 => 10.30.60.33 15001
Sun Sep 3 10:01:13 2023 TCP 65.109.103.215 15001 => 10.30.60.33 15001
Sun Sep 3 10:01:14 2023 TCP 65.109.103.215 15001 => 10.30.60.33 15001
Sun Sep 3 10:01:32 2023 TCP 65.109.103.215 15001 => 10.30.60.33 15001
Sun Sep 3 10:02:59 2023 TCP 65.109.103.215 15001 => 10.30.60.33 15001
Sun Sep 3 09:54:12 2023 TCP 65.109.103.215 15001 => 10.30.60.35 15001
Sun Sep 3 09:58:03 2023 TCP 65.109.103.215 15001 => 10.30.60.35 15001
Sun Sep 3 09:58:04 2023 TCP 65.109.103.215 15001 => 10.30.60.35 15001
Sun Sep 3 09:56:43 2023 TCP 65.109.103.215 15001 => 10.30.60.36 15001
Sun Sep 3 09:56:45 2023 TCP 65.109.103.215 15001 => 10.30.60.36 15001
Sun Sep 3 09:56:46 2023 TCP 65.109.103.215 15001 => 10.30.60.36 15001
Sun Sep 3 09:55:09 2023 TCP 65.109.103.215 15001 => 10.30.60.38 15001
Sun Sep 3 09:55:34 2023 TCP 65.109.103.215 15001 => 10.30.60.38 15001
Sun Sep 3 09:55:37 2023 TCP 65.109.103.215 15001 => 10.30.60.38 15001
Sun Sep 3 09:56:14 2023 TCP 65.109.103.215 15001 => 10.30.60.38 15001
Sun Sep 3 09:56:15 2023 TCP 65.109.103.215 15001 => 10.30.60.38 15001
Sun Sep 3 09:56:30 2023 TCP 65.109.103.215 15001 => 10.30.60.38 15001
Sun Sep 3 09:56:32 2023 TCP 65.109.103.215 15001 => 10.30.60.38 15001
Sun Sep 3 09:56:57 2023 TCP 65.109.103.215 15001 => 10.30.60.38 15001
Sun Sep 3 09:58:32 2023 TCP 65.109.103.215 15001 => 10.30.60.38 15001
Sun Sep 3 10:01:37 2023 TCP 65.109.103.215 15001 => 10.30.60.38 15001
Sun Sep 3 10:01:39 2023 TCP 65.109.103.215 15001 => 10.30.60.38 15001
Sun Sep 3 10:01:42 2023 TCP 65.109.103.215 15001 => 10.30.60.38 15001
Sun Sep 3 10:02:38 2023 TCP 65.109.103.215 15001 => 10.30.60.38 15001
Sun Sep 3 10:03:05 2023 TCP 65.109.103.215 15001 => 10.30.60.38 15001
Sun Sep 3 09:57:31 2023 TCP 65.109.103.215 15001 => 10.30.60.39 15001
Sun Sep 3 10:00:31 2023 TCP 65.109.103.215 15001 => 10.229.192.61 15001
Sun Sep 3 09:57:47 2023 TCP 65.109.103.215 15001 => 10.229.192.150 15001
Sun Sep 3 09:59:17 2023 TCP 65.109.103.215 15001 => 10.229.192.150 15001
Sun Sep 3 10:02:24 2023 TCP 65.109.103.215 15001 => 10.229.192.150 15001
Sun Sep 3 10:02:25 2023 TCP 65.109.103.215 15001 => 10.229.192.150 15001
Sun Sep 3 10:02:43 2023 TCP 65.109.103.215 15001 => 10.229.192.150 15001
Sun Sep 3 10:02:46 2023 TCP 65.109.103.215 15001 => 10.229.192.150 15001
Sun Sep 3 09:55:52 2023 TCP 65.109.103.215 15001 => 172.16.7.1 15001
Sun Sep 3 10:02:00 2023 TCP 65.109.103.215 15001 => 172.16.7.4 15001
Sun Sep 3 09:57:09 2023 TCP 65.109.103.215 15001 => 172.16.7.5 15001
Sun Sep 3 09:57:12 2023 TCP 65.109.103.215 15001 => 172.16.7.5 15001
Sun Sep 3 09:58:45 2023 TCP 65.109.103.215 15001 => 172.16.7.6 15001
Sun Sep 3 09:58:47 2023 TCP 65.109.103.215 15001 => 172.16.7.6 15001
Sun Sep 3 10:03:30 2023 TCP 65.109.103.215 15001 => 172.16.7.6 15001
Sun Sep 3 10:03:31 2023 TCP 65.109.103.215 15001 => 172.16.7.6 15001
Sun Sep 3 10:03:35 2023 TCP 65.109.103.215 15001 => 172.16.7.6 15001
Sun Sep 3 10:01:52 2023 TCP 65.109.103.215 15001 => 172.16.7.7 15001
Sun Sep 3 10:03:20 2023 TCP 65.109.103.215 15001 => 172.16.7.9 15001
Sun Sep 3 10:03:22 2023 TCP 65.109.103.215 15001 => 172.16.7.9 15001
Sun Sep 3 09:57:15 2023 TCP 65.109.103.215 15001 => 172.16.7.10 15001
Sun Sep 3 10:00:30 2023 TCP 65.109.103.215 15001 => 172.16.7.12 15001
Sun Sep 3 10:00:33 2023 TCP 65.109.103.215 15001 => 172.16.7.12 15001
Sun Sep 3 09:57:44 2023 TCP 65.109.103.215 15001 => 172.16.7.13 15001
Sun Sep 3 09:57:46 2023 TCP 65.109.103.215 15001 => 172.16.7.13 15001
Sun Sep 3 09:59:18 2023 TCP 65.109.103.215 15001 => 172.16.7.13 15001
Sun Sep 3 09:59:19 2023 TCP 65.109.103.215 15001 => 172.16.7.13 15001
Sun Sep 3 09:59:21 2023 TCP 65.109.103.215 15001 => 172.16.7.13 15001
Sun Sep 3 09:59:23 2023 TCP 65.109.103.215 15001 => 172.16.7.13 15001
Sun Sep 3 10:00:51 2023 TCP 65.109.103.215 15001 => 172.16.7.13 15001
Sun Sep 3 09:56:38 2023 TCP 65.109.103.215 15001 => 172.16.7.14 15001
Sun Sep 3 09:58:40 2023 TCP 65.109.103.215 15001 => 172.16.7.14 15001
Sun Sep 3 10:02:14 2023 TCP 65.109.103.215 15001 => 172.28.109.21 15001
Sun Sep 3 10:02:14 2023 TCP 65.109.103.215 15001 => 172.28.109.21 15001
Sun Sep 3 10:02:15 2023 TCP 65.109.103.215 15001 => 172.28.109.21 15001
Sun Sep 3 10:02:17 2023 TCP 65.109.103.215 15001 => 172.28.109.21 15001
Sun Sep 3 10:00:22 2023 TCP 65.109.103.215 15001 => 172.28.109.24 15001
Sun Sep 3 10:01:48 2023 TCP 65.109.103.215 15001 => 172.28.109.24 15001
Sun Sep 3 10:01:51 2023 TCP 65.109.103.215 15001 => 172.28.109.24 15001
Sun Sep 3 10:00:44 2023 TCP 65.109.103.215 15001 => 172.28.109.27 15001
Sun Sep 3 09:55:52 2023 TCP 65.109.103.215 15001 => 172.28.109.28 15001
Sun Sep 3 09:55:53 2023 TCP 65.109.103.215 15001 => 172.28.109.28 15001
Sun Sep 3 09:57:13 2023 TCP 65.109.103.215 15001 => 172.28.109.29 15001
Sun Sep 3 10:00:33 2023 TCP 65.109.103.215 15001 => 172.28.109.103 15001
Sun Sep 3 09:56:25 2023 TCP 65.109.103.215 15001 => 172.28.109.104 15001
Sun Sep 3 09:56:28 2023 TCP 65.109.103.215 15001 => 172.28.109.104 15001
Sun Sep 3 09:57:00 2023 TCP 65.109.103.215 15001 => 172.28.109.104 15001
Sun Sep 3 10:01:36 2023 TCP 65.109.103.215 15001 => 172.28.109.104 15001
Sun Sep 3 10:01:37 2023 TCP 65.109.103.215 15001 => 172.28.109.104 15001
Sun Sep 3 10:01:39 2023 TCP 65.109.103.215 15001 => 172.28.109.104 15001
Sun Sep 3 09:57:13 2023 TCP 65.109.103.215 15001 => 172.28.109.105 15001
Sun Sep 3 09:57:14 2023 TCP 65.109.103.215 15001 => 172.28.109.105 15001
Sun Sep 3 09:59:05 2023 TCP 65.109.103.215 15001 => 172.28.109.106 15001
Sun Sep 3 09:59:06 2023 TCP 65.109.103.215 15001 => 172.28.109.106 15001
Sun Sep 3 10:00:35 2023 TCP 65.109.103.215 15001 => 172.28.109.106 15001
Sun Sep 3 10:00:42 2023 TCP 65.109.103.215 15001 => 172.28.109.108 15001
Sun Sep 3 09:55:17 2023 TCP 65.109.103.215 15001 => 172.30.2.93 15001
Sun Sep 3 09:55:37 2023 TCP 65.109.103.215 15001 => 172.30.2.93 15001
Sun Sep 3 09:57:01 2023 TCP 65.109.103.215 15001 => 172.30.2.93 15001
Sun Sep 3 09:57:04 2023 TCP 65.109.103.215 15001 => 172.30.2.93 15001
Sun Sep 3 09:58:03 2023 TCP 65.109.103.215 15001 => 172.30.2.93 15001
Sun Sep 3 09:58:04 2023 TCP 65.109.103.215 15001 => 172.30.2.93 15001
Sun Sep 3 09:58:16 2023 TCP 65.109.103.215 15001 => 172.30.2.93 15001
Sun Sep 3 09:59:54 2023 TCP 65.109.103.215 15001 => 172.30.2.93 15001
Sun Sep 3 10:00:10 2023 TCP 65.109.103.215 15001 => 172.30.2.93 15001
Sun Sep 3 10:00:11 2023 TCP 65.109.103.215 15001 => 172.30.2.93 15001
Sun Sep 3 10:01:22 2023 TCP 65.109.103.215 15001 => 172.30.2.93 15001
Sun Sep 3 10:01:39 2023 TCP 65.109.103.215 15001 => 172.30.2.93 15001
Sun Sep 3 10:02:47 2023 TCP 65.109.103.215 15001 => 172.30.2.93 15001
Sun Sep 3 10:02:50 2023 TCP 65.109.103.215 15001 => 172.30.2.93 15001
Sun Sep 3 10:03:04 2023 TCP 65.109.103.215 15001 => 172.30.2.93 15001
Sun Sep 3 10:03:05 2023 TCP 65.109.103.215 15001 => 172.30.2.93 15001
Sun Sep 3 10:03:07 2023 TCP 65.109.103.215 15001 => 172.30.2.93 15001
Sun Sep 3 09:57:21 2023 TCP 65.109.103.215 15001 => 192.168.1.15 15001
Sun Sep 3 09:57:22 2023 TCP 65.109.103.215 15001 => 192.168.1.15 15001
Sun Sep 3 09:57:20 2023 TCP 65.109.103.215 15001 => 192.168.2.2 15001
Sun Sep 3 09:57:21 2023 TCP 65.109.103.215 15001 => 192.168.2.2 15001
Sun Sep 3 09:57:22 2023 TCP 65.109.103.215 15001 => 192.168.2.2 15001
Sun Sep 3 10:03:22 2023 TCP 65.109.103.215 15001 => 192.168.2.8 15001
Sun Sep 3 09:55:20 2023 TCP 65.109.103.215 15001 => 192.168.2.12 15001
Sun Sep 3 09:55:22 2023 TCP 65.109.103.215 15001 => 192.168.2.12 15001
Sun Sep 3 10:00:22 2023 TCP 65.109.103.215 15001 => 192.168.2.16 15001
Sun Sep 3 09:57:03 2023 TCP 65.109.103.215 15001 => 192.168.3.20 15001
Sun Sep 3 09:59:28 2023 TCP 65.109.103.215 15001 => 192.168.3.20 15001
Sun Sep 3 09:59:42 2023 TCP 65.109.103.215 15001 => 192.168.3.20 15001
Sun Sep 3 09:59:45 2023 TCP 65.109.103.215 15001 => 192.168.3.20 15001
Sun Sep 3 10:00:57 2023 TCP 65.109.103.215 15001 => 192.168.3.20 15001
Sun Sep 3 09:57:14 2023 TCP 65.109.103.215 15001 => 192.168.3.23 15001
Sun Sep 3 09:57:17 2023 TCP 65.109.103.215 15001 => 192.168.3.23 15001
Sun Sep 3 09:55:06 2023 TCP 65.109.103.215 15001 => 192.168.3.24 15001
Sun Sep 3 09:55:34 2023 TCP 65.109.103.215 15001 => 192.168.3.24 15001
Sun Sep 3 09:56:02 2023 TCP 65.109.103.215 15001 => 192.168.3.24 15001
Sun Sep 3 09:56:21 2023 TCP 65.109.103.215 15001 => 192.168.3.24 15001
Sun Sep 3 09:56:22 2023 TCP 65.109.103.215 15001 => 192.168.3.24 15001
Sun Sep 3 09:56:24 2023 TCP 65.109.103.215 15001 => 192.168.3.24 15001
Sun Sep 3 09:58:21 2023 TCP 65.109.103.215 15001 => 192.168.3.24 15001
Sun Sep 3 09:59:42 2023 TCP 65.109.103.215 15001 => 192.168.3.24 15001
Sun Sep 3 09:59:44 2023 TCP 65.109.103.215 15001 => 192.168.3.24 15001
Sun Sep 3 10:01:33 2023 TCP 65.109.103.215 15001 => 192.168.3.24 15001
Sun Sep 3 10:02:59 2023 TCP 65.109.103.215 15001 => 192.168.3.24 15001
Sun Sep 3 09:57:33 2023 TCP 65.109.103.215 15001 => 192.168.3.25 15001
Sun Sep 3 10:02:14 2023 TCP 65.109.103.215 15001 => 192.168.3.25 15001
Sun Sep 3 10:02:14 2023 TCP 65.109.103.215 15001 => 192.168.3.25 15001
Sun Sep 3 10:02:15 2023 TCP 65.109.103.215 15001 => 192.168.3.25 15001
Sun Sep 3 10:02:17 2023 TCP 65.109.103.215 15001 => 192.168.3.25 15001
Sun Sep 3 09:57:49 2023 TCP 65.109.103.215 15001 => 192.168.3.28 15001
Sun Sep 3 09:57:27 2023 TCP 65.109.103.215 15001 => 192.168.3.112 15001
Sun Sep 3 09:59:06 2023 TCP 65.109.103.215 15001 => 192.168.3.128 15001
Sun Sep 3 09:57:16 2023 TCP 65.109.103.215 15001 => 192.168.3.129 15001
Sun Sep 3 09:57:18 2023 TCP 65.109.103.215 15001 => 192.168.3.129 15001
Sun Sep 3 10:01:55 2023 TCP 65.109.103.215 15001 => 192.168.5.17 15001
Sun Sep 3 10:01:55 2023 TCP 65.109.103.215 15001 => 192.168.5.17 15001
Sun Sep 3 09:57:37 2023 TCP 65.109.103.215 15001 => 192.168.7.91 15001
Sun Sep 3 09:57:38 2023 TCP 65.109.103.215 15001 => 192.168.7.91 15001
Sun Sep 3 09:54:31 2023 TCP 65.109.103.215 15001 => 192.168.7.92 15001
Sun Sep 3 09:57:49 2023 TCP 65.109.103.215 15001 => 192.168.7.92 15001
Sun Sep 3 09:59:13 2023 TCP 65.109.103.215 15001 => 192.168.7.92 15001
Sun Sep 3 10:02:25 2023 TCP 65.109.103.215 15001 => 192.168.7.92 15001
Sun Sep 3 10:02:30 2023 TCP 65.109.103.215 15001 => 192.168.7.92 15001
Sun Sep 3 10:02:44 2023 TCP 65.109.103.215 15001 => 192.168.7.92 15001
Sun Sep 3 10:00:57 2023 TCP 65.109.103.215 15001 => 192.168.7.96 15001
Sun Sep 3 10:03:12 2023 TCP 65.109.103.215 15001 => 192.168.10.3 15001
Sun Sep 3 09:54:46 2023 TCP 65.109.103.215 15001 => 192.168.10.4 15001
Sun Sep 3 09:54:47 2023 TCP 65.109.103.215 15001 => 192.168.10.4 15001
Sun Sep 3 10:03:25 2023 TCP 65.109.103.215 15001 => 192.168.10.4 15001
Sun Sep 3 09:57:30 2023 TCP 65.109.103.215 15001 => 192.168.10.21 15001
Sun Sep 3 10:02:12 2023 TCP 65.109.103.215 15001 => 192.168.10.21 15001
Sun Sep 3 10:02:14 2023 TCP 65.109.103.215 15001 => 192.168.10.21 15001
Sun Sep 3 10:02:15 2023 TCP 65.109.103.215 15001 => 192.168.10.21 15001
Sun Sep 3 10:02:17 2023 TCP 65.109.103.215 15001 => 192.168.10.21 15001
Sun Sep 3 10:02:03 2023 TCP 65.109.103.215 15001 => 192.168.10.22 15001
Sun Sep 3 09:55:39 2023 TCP 65.109.103.215 15001 => 192.168.10.23 15001
Sun Sep 3 09:58:59 2023 TCP 65.109.103.215 15001 => 192.168.10.24 15001
Sun Sep 3 10:03:25 2023 TCP 65.109.103.215 15001 => 192.168.10.27 15001
Sun Sep 3 10:03:26 2023 TCP 65.109.103.215 15001 => 192.168.10.27 15001
Sun Sep 3 09:59:03 2023 TCP 65.109.103.215 15001 => 192.168.25.152 15001
Sun Sep 3 10:02:20 2023 TCP 65.109.103.215 15001 => 192.168.25.153 15001
Sun Sep 3 09:55:11 2023 TCP 65.109.103.215 15001 => 192.168.25.156 15001
Sun Sep 3 09:58:32 2023 TCP 65.109.103.215 15001 => 192.168.25.156 15001
Sun Sep 3 09:59:36 2023 TCP 65.109.103.215 15001 => 192.168.25.156 15001
Sun Sep 3 09:59:38 2023 TCP 65.109.103.215 15001 => 192.168.25.156 15001
Sun Sep 3 09:59:50 2023 TCP 65.109.103.215 15001 => 192.168.25.156 15001
Sun Sep 3 10:01:11 2023 TCP 65.109.103.215 15001 => 192.168.25.156 15001
Sun Sep 3 10:01:24 2023 TCP 65.109.103.215 15001 => 192.168.25.156 15001
Sun Sep 3 10:01:38 2023 TCP 65.109.103.215 15001 => 192.168.25.156 15001
Sun Sep 3 10:01:42 2023 TCP 65.109.103.215 15001 => 192.168.25.156 15001
Sun Sep 3 10:02:45 2023 TCP 65.109.103.215 15001 => 192.168.25.156 15001
Sun Sep 3 10:02:46 2023 TCP 65.109.103.215 15001 => 192.168.25.156 15001
Sun Sep 3 09:57:13 2023 TCP 65.109.103.215 15001 => 192.168.25.160 15001
Sun Sep 3 10:03:26 2023 TCP 65.109.103.215 15001 => 192.168.25.161 15001
Sun Sep 3 09:57:47 2023 TCP 65.109.103.215 15001 => 192.168.25.165 15001
Sun Sep 3 09:58:52 2023 TCP 65.109.103.215 15001 => 192.168.25.166 15001
Sun Sep 3 09:58:56 2023 TCP 65.109.103.215 15001 => 192.168.25.166 15001
Sun Sep 3 09:57:43 2023 TCP 65.109.103.215 15001 => 192.168.31.51 15001
Sun Sep 3 09:57:49 2023 TCP 65.109.103.215 15001 => 192.168.31.56 15001
Sun Sep 3 09:59:18 2023 TCP 65.109.103.215 15001 => 192.168.31.56 15001
Sun Sep 3 10:02:48 2023 TCP 65.109.103.215 15001 => 192.168.31.56 15001
Sun Sep 3 10:01:50 2023 TCP 65.109.103.215 15001 => 192.168.31.60 15001
Sun Sep 3 10:02:44 2023 TCP 65.109.103.215 15001 => 192.168.31.62 15001
Sun Sep 3 09:58:45 2023 TCP 65.109.103.215 15001 => 192.168.31.67 15001
Sun Sep 3 09:54:31 2023 TCP 65.109.103.215 15001 => 192.168.31.70 15001
Sun Sep 3 09:54:50 2023 TCP 65.109.103.215 15001 => 192.168.31.70 15001
Sun Sep 3 10:00:57 2023 TCP 65.109.103.215 15001 => 192.168.31.70 15001
Sun Sep 3 10:00:58 2023 TCP 65.109.103.215 15001 => 192.168.31.70 15001
Sun Sep 3 10:01:00 2023 TCP 65.109.103.215 15001 => 192.168.31.70 15001
Sun Sep 3 10:03:29 2023 TCP 65.109.103.215 15001 => 192.168.31.73 15001
Sun Sep 3 10:03:31 2023 TCP 65.109.103.215 15001 => 192.168.31.73 15001
Sun Sep 3 10:03:35 2023 TCP 65.109.103.215 15001 => 192.168.31.73 15001
Sun Sep 3 09:54:12 2023 TCP 65.109.103.215 15001 => 192.168.31.75 15001
Sun Sep 3 09:54:43 2023 TCP 65.109.103.215 15001 => 192.168.31.75 15001
Sun Sep 3 10:02:01 2023 TCP 65.109.103.215 15001 => 192.168.31.76 15001
Sun Sep 3 10:02:05 2023 TCP 65.109.103.215 15001 => 192.168.31.76 15001
Sun Sep 3 09:57:47 2023 TCP 65.109.103.215 15001 => 192.168.31.77 15001
Sun Sep 3 09:54:29 2023 TCP 65.109.103.215 15001 => 192.168.31.78 15001
Sun Sep 3 09:54:40 2023 TCP 65.109.103.215 15001 => 192.168.31.78 15001
Sun Sep 3 09:54:45 2023 TCP 65.109.103.215 15001 => 192.168.31.78 15001
Sun Sep 3 09:56:58 2023 TCP 65.109.103.215 15001 => 192.168.31.78 15001
Sun Sep 3 09:59:35 2023 TCP 65.109.103.215 15001 => 192.168.31.78 15001
Sun Sep 3 09:59:36 2023 TCP 65.109.103.215 15001 => 192.168.31.78 15001
Sun Sep 3 09:59:38 2023 TCP 65.109.103.215 15001 => 192.168.31.78 15001
Sun Sep 3 10:00:13 2023 TCP 65.109.103.215 15001 => 192.168.31.78 15001
Sun Sep 3 10:00:16 2023 TCP 65.109.103.215 15001 => 192.168.31.78 15001
Sun Sep 3 10:01:21 2023 TCP 65.109.103.215 15001 => 192.168.31.78 15001
Sun Sep 3 10:01:24 2023 TCP 65.109.103.215 15001 => 192.168.31.78 15001
Sun Sep 3 10:03:03 2023 TCP 65.109.103.215 15001 => 192.168.31.78 15001
Sun Sep 3 10:03:04 2023 TCP 65.109.103.215 15001 => 192.168.31.78 15001
Sun Sep 3 09:57:17 2023 TCP 65.109.103.215 15001 => 192.168.77.101 15001
Sun Sep 3 09:57:12 2023 TCP 65.109.103.215 15001 => 192.168.77.102 15001
Sun Sep 3 09:57:12 2023 TCP 65.109.103.215 15001 => 192.168.77.103 15001
Sun Sep 3 10:03:29 2023 TCP 65.109.103.215 15001 => 192.168.77.104 15001
Sun Sep 3 10:03:35 2023 TCP 65.109.103.215 15001 => 192.168.77.104 15001
Sun Sep 3 09:57:18 2023 TCP 65.109.103.215 15001 => 192.168.77.106 15001
Sun Sep 3 09:55:06 2023 TCP 65.109.103.215 15001 => 192.168.77.246 15001
Sun Sep 3 09:56:05 2023 TCP 65.109.103.215 15001 => 192.168.77.246 15001
Sun Sep 3 09:56:14 2023 TCP 65.109.103.215 15001 => 192.168.77.246 15001
Sun Sep 3 09:56:28 2023 TCP 65.109.103.215 15001 => 192.168.77.246 15001
Sun Sep 3 09:56:30 2023 TCP 65.109.103.215 15001 => 192.168.77.246 15001
Sun Sep 3 09:56:32 2023 TCP 65.109.103.215 15001 => 192.168.77.246 15001
Sun Sep 3 09:56:57 2023 TCP 65.109.103.215 15001 => 192.168.77.246 15001
Sun Sep 3 09:56:59 2023 TCP 65.109.103.215 15001 => 192.168.77.246 15001
Sun Sep 3 09:58:26 2023 TCP 65.109.103.215 15001 => 192.168.77.246 15001
Sun Sep 3 09:58:27 2023 TCP 65.109.103.215 15001 => 192.168.77.246 15001
Sun Sep 3 10:00:05 2023 TCP 65.109.103.215 15001 => 192.168.77.246 15001
Sun Sep 3 10:01:12 2023 TCP 65.109.103.215 15001 => 192.168.77.246 15001
Sun Sep 3 10:03:00 2023 TCP 65.109.103.215 15001 => 192.168.77.246 15001
Sun Sep 3 10:03:02 2023 TCP 65.109.103.215 15001 => 192.168.77.246 15001
Sun Sep 3 10:01:48 2023 TCP 65.109.103.215 15001 => 192.168.77.247 15001
Sun Sep 3 09:57:59 2023 TCP 65.109.103.215 15001 => 192.168.101.103 15001
Sun Sep 3 09:59:26 2023 TCP 65.109.103.215 15001 => 192.168.101.103 15001
Sun Sep 3 10:02:35 2023 TCP 65.109.103.215 15001 => 192.168.101.103 15001
Sun Sep 3 10:02:37 2023 TCP 65.109.103.215 15001 => 192.168.101.103 15001
Sun Sep 3 09:57:09 2023 TCP 65.109.103.215 15001 => 192.168.101.104 15001
Sun Sep 3 09:57:12 2023 TCP 65.109.103.215 15001 => 192.168.101.104 15001
Sun Sep 3 10:00:24 2023 TCP 65.109.103.215 15001 => 192.168.110.25 15001
Sun Sep 3 10:00:28 2023 TCP 65.109.103.215 15001 => 192.168.110.25 15001
Sun Sep 3 10:01:50 2023 TCP 65.109.103.215 15001 => 192.168.110.25 15001
Sun Sep 3 10:01:51 2023 TCP 65.109.103.215 15001 => 192.168.110.25 15001
Sun Sep 3 09:58:56 2023 TCP 65.109.103.215 15001 => 192.168.110.76 15001
Sun Sep 3 10:03:37 2023 TCP 65.109.103.215 15001 => 192.168.110.76 15001
Sun Sep 3 10:03:22 2023 TCP 65.109.103.215 15001 => 192.168.110.130 15001
Sun Sep 3 10:03:25 2023 TCP 65.109.103.215 15001 => 192.168.110.130 15001
Sun Sep 3 09:59:35 2023 TCP 65.109.103.215 15001 => 192.168.138.130 15001
Sun Sep 3 09:59:36 2023 TCP 65.109.103.215 15001 => 192.168.138.130 15001
Sun Sep 3 09:59:38 2023 TCP 65.109.103.215 15001 => 192.168.138.130 15001
Sun Sep 3 10:01:08 2023 TCP 65.109.103.215 15001 => 192.168.138.130 15001
Sun Sep 3 10:01:09 2023 TCP 65.109.103.215 15001 => 192.168.138.130 15001
Sun Sep 3 10:01:11 2023 TCP 65.109.103.215 15001 => 192.168.138.130 15001
Sun Sep 3 09:57:49 2023 TCP 65.109.103.215 15001 => 192.168.15.30 16004
Sun Sep 3 09:59:18 2023 TCP 65.109.103.215 15001 => 192.168.15.30 16004
Sun Sep 3 09:57:09 2023 TCP 65.109.103.215 15001 => 192.168.1.2 60465
Sun Sep 3 09:57:12 2023 TCP 65.109.103.215 15001 => 192.168.1.2 60465
Sun Sep 3 10:00:20 2023 TCP 65.109.103.215 15001 => 10.109.55.127 40004
Sun Sep 3 09:57:10 2023 TCP 65.109.103.215 15001 => 192.168.7.88 15004
Sun Sep 3 09:57:09 2023 TCP 65.109.103.215 15001 => 172.18.0.4 6929
Sun Sep 3 09:59:25 2023 TCP 65.109.103.215 15001 => 172.18.0.4 6929
Sun Sep 3 09:56:34 2023 TCP 65.109.103.215 15001 => 10.104.216.106 40010
Sun Sep 3 09:57:15 2023 TCP 65.109.103.215 15001 => 10.100.97.80 40023
Sun Sep 3 10:00:44 2023 TCP 65.109.103.215 15001 => 10.9.11.7 6797
Sun Sep 3 09:59:19 2023 TCP 65.109.103.215 15001 => 10.111.40.238 40045
Sun Sep 3 09:59:21 2023 TCP 65.109.103.215 15001 => 10.111.40.238 40045
Sun Sep 3 09:59:23 2023 TCP 65.109.103.215 15001 => 10.111.40.238 40045
Sun Sep 3 10:02:20 2023 TCP 65.109.103.215 15001 => 10.111.40.238 40045
Sun Sep 3 09:57:13 2023 TCP 65.109.103.215 15001 => 10.9.11.7 6799
Sun Sep 3 10:02:14 2023 TCP 65.109.103.215 15001 => 10.9.11.7 6950
Sun Sep 3 10:02:14 2023 TCP 65.109.103.215 15001 => 10.9.11.7 6950
Sun Sep 3 10:02:15 2023 TCP 65.109.103.215 15001 => 10.9.11.7 6950
Sun Sep 3 10:02:17 2023 TCP 65.109.103.215 15001 => 10.9.11.7 6950
Sun Sep 3 10:02:02 2023 TCP 65.109.103.215 15001 => 192.168.1.9 15003
Sun Sep 3 09:58:52 2023 TCP 65.109.103.215 15001 => 192.168.7.90 15003
Sun Sep 3 09:58:54 2023 TCP 65.109.103.215 15001 => 192.168.7.90 15003
Sun Sep 3 09:56:11 2023 TCP 65.109.103.215 15001 => 192.168.20.203 15003
Sun Sep 3 09:59:03 2023 TCP 65.109.103.215 15001 => 10.42.22.25 51005
Sun Sep 3 10:02:19 2023 TCP 65.109.103.215 15001 => 10.42.29.23 51005
Sun Sep 3 10:02:20 2023 TCP 65.109.103.215 15001 => 10.42.29.23 51005
Sun Sep 3 09:57:38 2023 TCP 65.109.103.215 15001 => 10.42.30.40 51005
Sun Sep 3 09:55:11 2023 TCP 65.109.103.215 15001 => 10.42.31.23 51005
Sun Sep 3 09:55:17 2023 TCP 65.109.103.215 15001 => 10.42.31.23 51005
Sun Sep 3 09:57:00 2023 TCP 65.109.103.215 15001 => 10.42.31.23 51005
Sun Sep 3 09:58:13 2023 TCP 65.109.103.215 15001 => 10.42.31.23 51005
Sun Sep 3 09:58:30 2023 TCP 65.109.103.215 15001 => 10.42.31.23 51005
Sun Sep 3 09:58:32 2023 TCP 65.109.103.215 15001 => 10.42.31.23 51005
Sun Sep 3 10:00:13 2023 TCP 65.109.103.215 15001 => 10.42.31.23 51005
Sun Sep 3 10:00:16 2023 TCP 65.109.103.215 15001 => 10.42.31.23 51005
Sun Sep 3 10:01:02 2023 TCP 65.109.103.215 15001 => 10.42.31.23 51005
Sun Sep 3 10:01:04 2023 TCP 65.109.103.215 15001 => 10.42.31.23 51005
Sun Sep 3 10:01:22 2023 TCP 65.109.103.215 15001 => 10.42.31.23 51005
Sun Sep 3 10:01:39 2023 TCP 65.109.103.215 15001 => 10.42.31.23 51005
Sun Sep 3 10:01:42 2023 TCP 65.109.103.215 15001 => 10.42.31.23 51005
Sun Sep 3 10:03:07 2023 TCP 65.109.103.215 15001 => 10.42.31.23 51005
Sun Sep 3 09:57:35 2023 TCP 65.109.103.215 15001 => 10.42.32.27 51005
Sun Sep 3 09:57:38 2023 TCP 65.109.103.215 15001 => 10.42.32.27 51005
Sun Sep 3 10:02:03 2023 TCP 65.109.103.215 15001 => 10.42.32.27 51005
Sun Sep 3 10:00:49 2023 TCP 65.109.103.215 15001 => 10.42.34.21 51005
Sun Sep 3 09:55:01 2023 TCP 65.109.103.215 15001 => 10.42.37.22 51005
Sun Sep 3 09:55:29 2023 TCP 65.109.103.215 15001 => 10.42.37.22 51005
Sun Sep 3 09:55:30 2023 TCP 65.109.103.215 15001 => 10.42.37.22 51005
Sun Sep 3 09:55:32 2023 TCP 65.109.103.215 15001 => 10.42.37.22 51005
Sun Sep 3 09:56:55 2023 TCP 65.109.103.215 15001 => 10.42.37.22 51005
Sun Sep 3 09:58:20 2023 TCP 65.109.103.215 15001 => 10.42.37.22 51005
Sun Sep 3 09:59:30 2023 TCP 65.109.103.215 15001 => 10.42.37.22 51005
Sun Sep 3 09:59:48 2023 TCP 65.109.103.215 15001 => 10.42.37.22 51005
Sun Sep 3 09:59:51 2023 TCP 65.109.103.215 15001 => 10.42.37.22 51005
Sun Sep 3 10:00:03 2023 TCP 65.109.103.215 15001 => 10.42.37.22 51005
Sun Sep 3 10:01:22 2023 TCP 65.109.103.215 15001 => 10.42.37.22 51005
Sun Sep 3 10:01:31 2023 TCP 65.109.103.215 15001 => 10.42.37.22 51005
Sun Sep 3 10:01:32 2023 TCP 65.109.103.215 15001 => 10.42.37.22 51005
Sun Sep 3 10:02:47 2023 TCP 65.109.103.215 15001 => 10.42.37.22 51005
Sun Sep 3 09:53:57 2023 TCP 65.109.103.215 15001 => 10.42.39.25 51005
Sun Sep 3 09:54:00 2023 TCP 65.109.103.215 15001 => 10.42.39.25 51005
Sun Sep 3 09:54:08 2023 TCP 65.109.103.215 15001 => 10.42.39.25 51005
Sun Sep 3 09:54:27 2023 TCP 65.109.103.215 15001 => 10.42.39.25 51005
Sun Sep 3 09:54:44 2023 TCP 65.109.103.215 15001 => 10.42.39.25 51005
Sun Sep 3 09:58:04 2023 TCP 65.109.103.215 15001 => 10.42.39.25 51005
Sun Sep 3 09:58:05 2023 TCP 65.109.103.215 15001 => 10.42.39.25 51005
Sun Sep 3 09:58:07 2023 TCP 65.109.103.215 15001 => 10.42.39.25 51005
Sun Sep 3 09:58:08 2023 TCP 65.109.103.215 15001 => 10.42.39.25 51005
Sun Sep 3 09:59:36 2023 TCP 65.109.103.215 15001 => 10.42.39.25 51005
Sun Sep 3 09:59:49 2023 TCP 65.109.103.215 15001 => 10.42.39.25 51005
Sun Sep 3 09:59:50 2023 TCP 65.109.103.215 15001 => 10.42.39.25 51005
Sun Sep 3 09:59:52 2023 TCP 65.109.103.215 15001 => 10.42.39.25 51005
Sun Sep 3 09:59:54 2023 TCP 65.109.103.215 15001 => 10.42.39.25 51005
Sun Sep 3 10:00:06 2023 TCP 65.109.103.215 15001 => 10.42.39.25 51005
Sun Sep 3 09:56:45 2023 TCP 65.109.103.215 15001 => 10.42.40.27 51005
Sun Sep 3 09:56:46 2023 TCP 65.109.103.215 15001 => 10.42.40.27 51005
Sun Sep 3 09:58:13 2023 TCP 65.109.103.215 15001 => 10.42.41.35 51005
Sun Sep 3 09:58:20 2023 TCP 65.109.103.215 15001 => 10.42.41.35 51005
Sun Sep 3 09:58:21 2023 TCP 65.109.103.215 15001 => 10.42.41.35 51005
Sun Sep 3 10:02:43 2023 TCP 65.109.103.215 15001 => 10.42.41.35 51005
Sun Sep 3 10:01:47 2023 TCP 65.109.103.215 15001 => 10.42.42.26 51005
Sun Sep 3 10:01:48 2023 TCP 65.109.103.215 15001 => 10.42.42.26 51005
Sun Sep 3 10:01:50 2023 TCP 65.109.103.215 15001 => 10.42.42.26 51005
Sun Sep 3 10:00:20 2023 TCP 65.109.103.215 15001 => 10.42.43.29 51005
Sun Sep 3 10:00:23 2023 TCP 65.109.103.215 15001 => 10.42.43.29 51005
Sun Sep 3 10:01:47 2023 TCP 65.109.103.215 15001 => 10.42.43.29 51005
Sun Sep 3 10:01:50 2023 TCP 65.109.103.215 15001 => 10.42.43.29 51005
Sun Sep 3 10:00:28 2023 TCP 65.109.103.215 15001 => 10.42.47.23 51005
Sun Sep 3 10:02:22 2023 TCP 65.109.103.215 15001 => 10.42.49.28 51005
Sun Sep 3 10:02:24 2023 TCP 65.109.103.215 15001 => 10.42.49.28 51005
Sun Sep 3 09:58:58 2023 TCP 65.109.103.215 15001 => 10.42.52.44 51005
Sun Sep 3 09:59:01 2023 TCP 65.109.103.215 15001 => 10.42.52.44 51005
Sun Sep 3 09:57:38 2023 TCP 65.109.103.215 15001 => 10.42.59.12 51005
Sun Sep 3 09:57:40 2023 TCP 65.109.103.215 15001 => 10.42.59.12 51005
Sun Sep 3 09:55:33 2023 TCP 65.109.103.215 15001 => 10.42.60.13 51005
Sun Sep 3 09:56:14 2023 TCP 65.109.103.215 15001 => 10.42.60.13 51005
Sun Sep 3 09:58:06 2023 TCP 65.109.103.215 15001 => 10.42.60.13 51005
Sun Sep 3 09:58:08 2023 TCP 65.109.103.215 15001 => 10.42.60.13 51005
Sun Sep 3 09:58:26 2023 TCP 65.109.103.215 15001 => 10.42.60.13 51005
Sun Sep 3 10:01:22 2023 TCP 65.109.103.215 15001 => 10.42.60.13 51005
Sun Sep 3 10:01:35 2023 TCP 65.109.103.215 15001 => 10.42.60.13 51005
Sun Sep 3 10:01:36 2023 TCP 65.109.103.215 15001 => 10.42.60.13 51005
Sun Sep 3 10:01:38 2023 TCP 65.109.103.215 15001 => 10.42.60.13 51005
Sun Sep 3 10:03:00 2023 TCP 65.109.103.215 15001 => 10.42.60.13 51005
Sun Sep 3 09:57:49 2023 TCP 65.109.103.215 15001 => 192.168.15.27 16003
Sun Sep 3 10:02:20 2023 TCP 65.109.103.215 15001 => 192.168.15.27 16003
Sun Sep 3 10:02:22 2023 TCP 65.109.103.215 15001 => 192.168.15.27 16003
Sun Sep 3 10:03:31 2023 TCP 65.109.103.215 15001 => 10.30.60.11 15002
Sun Sep 3 10:03:35 2023 TCP 65.109.103.215 15001 => 10.30.60.11 15002
Sun Sep 3 10:00:31 2023 TCP 65.109.103.215 15001 => 192.168.7.89 15002
Sun Sep 3 09:54:31 2023 TCP 65.109.103.215 15001 => 192.168.7.93 15002
Sun Sep 3 09:56:08 2023 TCP 65.109.103.215 15001 => 192.168.7.93 15002
Sun Sep 3 09:56:11 2023 TCP 65.109.103.215 15001 => 192.168.7.93 15002
Sun Sep 3 09:59:21 2023 TCP 65.109.103.215 15001 => 192.168.7.93 15002
Sun Sep 3 10:02:23 2023 TCP 65.109.103.215 15001 => 192.168.7.93 15002
Sun Sep 3 10:02:42 2023 TCP 65.109.103.215 15001 => 192.168.7.93 15002
Sun Sep 3 10:00:30 2023 TCP 65.109.103.215 15001 => 192.168.7.98 15002
Sun Sep 3 09:55:06 2023 TCP 65.109.103.215 15001 => 192.168.20.202 15002
Sun Sep 3 09:55:08 2023 TCP 65.109.103.215 15001 => 192.168.20.202 15002
Sun Sep 3 09:55:32 2023 TCP 65.109.103.215 15001 => 192.168.20.202 15002
Sun Sep 3 10:02:59 2023 TCP 65.109.103.215 15001 => 192.168.20.202 15002
Sun Sep 3 10:03:02 2023 TCP 65.109.103.215 15001 => 192.168.20.202 15002
Sun Sep 3 09:57:09 2023 TCP 65.109.103.215 15001 => 10.106.233.68 40020
Sun Sep 3 10:03:30 2023 TCP 65.109.103.215 15001 => 10.106.233.66 40013
Sun Sep 3 09:55:51 2023 TCP 65.109.103.215 15001 => 10.42.22.24 51004
Sun Sep 3 10:02:07 2023 TCP 65.109.103.215 15001 => 10.42.24.25 51004
Sun Sep 3 10:02:08 2023 TCP 65.109.103.215 15001 => 10.42.24.25 51004
Sun Sep 3 09:55:17 2023 TCP 65.109.103.215 15001 => 10.42.27.27 51004
Sun Sep 3 09:55:39 2023 TCP 65.109.103.215 15001 => 10.42.27.27 51004
Sun Sep 3 09:56:29 2023 TCP 65.109.103.215 15001 => 10.42.27.27 51004
Sun Sep 3 09:57:00 2023 TCP 65.109.103.215 15001 => 10.42.27.27 51004
Sun Sep 3 09:57:03 2023 TCP 65.109.103.215 15001 => 10.42.27.27 51004
Sun Sep 3 09:58:32 2023 TCP 65.109.103.215 15001 => 10.42.27.27 51004
Sun Sep 3 09:59:49 2023 TCP 65.109.103.215 15001 => 10.42.27.27 51004
Sun Sep 3 09:59:52 2023 TCP 65.109.103.215 15001 => 10.42.27.27 51004
Sun Sep 3 09:59:54 2023 TCP 65.109.103.215 15001 => 10.42.27.27 51004
Sun Sep 3 10:01:08 2023 TCP 65.109.103.215 15001 => 10.42.27.27 51004
Sun Sep 3 10:01:11 2023 TCP 65.109.103.215 15001 => 10.42.27.27 51004
Sun Sep 3 10:01:22 2023 TCP 65.109.103.215 15001 => 10.42.27.27 51004
Sun Sep 3 10:02:50 2023 TCP 65.109.103.215 15001 => 10.42.27.27 51004
Sun Sep 3 10:03:07 2023 TCP 65.109.103.215 15001 => 10.42.27.27 51004
Sun Sep 3 10:03:10 2023 TCP 65.109.103.215 15001 => 10.42.27.27 51004
Sun Sep 3 09:56:39 2023 TCP 65.109.103.215 15001 => 10.42.29.24 51004
Sun Sep 3 09:56:40 2023 TCP 65.109.103.215 15001 => 10.42.29.24 51004
Sun Sep 3 09:59:05 2023 TCP 65.109.103.215 15001 => 10.42.31.21 51004
Sun Sep 3 09:59:05 2023 TCP 65.109.103.215 15001 => 10.42.32.21 51004
Sun Sep 3 09:57:50 2023 TCP 65.109.103.215 15001 => 10.42.33.24 51004
Sun Sep 3 09:59:14 2023 TCP 65.109.103.215 15001 => 10.42.33.24 51004
Sun Sep 3 09:59:17 2023 TCP 65.109.103.215 15001 => 10.42.33.24 51004
Sun Sep 3 10:02:25 2023 TCP 65.109.103.215 15001 => 10.42.33.24 51004
Sun Sep 3 10:02:30 2023 TCP 65.109.103.215 15001 => 10.42.33.24 51004
Sun Sep 3 09:53:47 2023 TCP 65.109.103.215 15001 => 10.42.36.22 51004
Sun Sep 3 09:53:49 2023 TCP 65.109.103.215 15001 => 10.42.36.22 51004
Sun Sep 3 09:57:58 2023 TCP 65.109.103.215 15001 => 10.42.36.22 51004
Sun Sep 3 09:57:59 2023 TCP 65.109.103.215 15001 => 10.42.36.22 51004
Sun Sep 3 09:58:01 2023 TCP 65.109.103.215 15001 => 10.42.36.22 51004
Sun Sep 3 09:59:47 2023 TCP 65.109.103.215 15001 => 10.42.36.22 51004
Sun Sep 3 09:59:50 2023 TCP 65.109.103.215 15001 => 10.42.36.22 51004
Sun Sep 3 09:59:51 2023 TCP 65.109.103.215 15001 => 10.42.36.22 51004
Sun Sep 3 09:59:53 2023 TCP 65.109.103.215 15001 => 10.42.36.22 51004
Sun Sep 3 10:01:00 2023 TCP 65.109.103.215 15001 => 10.42.36.22 51004
Sun Sep 3 10:01:04 2023 TCP 65.109.103.215 15001 => 10.42.36.22 51004
Sun Sep 3 10:02:40 2023 TCP 65.109.103.215 15001 => 10.42.36.22 51004
Sun Sep 3 09:55:17 2023 TCP 65.109.103.215 15001 => 10.42.37.23 51004
Sun Sep 3 10:01:04 2023 TCP 65.109.103.215 15001 => 10.42.37.23 51004
Sun Sep 3 10:01:23 2023 TCP 65.109.103.215 15001 => 10.42.37.23 51004
Sun Sep 3 10:02:47 2023 TCP 65.109.103.215 15001 => 10.42.37.23 51004
Sun Sep 3 10:03:11 2023 TCP 65.109.103.215 15001 => 10.42.37.23 51004
Sun Sep 3 10:03:27 2023 TCP 65.109.103.215 15001 => 10.42.39.22 51004
Sun Sep 3 10:00:53 2023 TCP 65.109.103.215 15001 => 10.42.41.34 51004
Sun Sep 3 10:00:55 2023 TCP 65.109.103.215 15001 => 10.42.41.34 51004
Sun Sep 3 09:55:07 2023 TCP 65.109.103.215 15001 => 10.42.42.22 51004
Sun Sep 3 09:55:09 2023 TCP 65.109.103.215 15001 => 10.42.42.22 51004
Sun Sep 3 09:56:15 2023 TCP 65.109.103.215 15001 => 10.42.42.22 51004
Sun Sep 3 09:56:28 2023 TCP 65.109.103.215 15001 => 10.42.42.22 51004
Sun Sep 3 09:56:29 2023 TCP 65.109.103.215 15001 => 10.42.42.22 51004
Sun Sep 3 09:56:30 2023 TCP 65.109.103.215 15001 => 10.42.42.22 51004
Sun Sep 3 09:56:32 2023 TCP 65.109.103.215 15001 => 10.42.42.22 51004
Sun Sep 3 09:56:56 2023 TCP 65.109.103.215 15001 => 10.42.42.22 51004
Sun Sep 3 09:58:26 2023 TCP 65.109.103.215 15001 => 10.42.42.22 51004
Sun Sep 3 10:00:12 2023 TCP 65.109.103.215 15001 => 10.42.42.22 51004
Sun Sep 3 10:00:13 2023 TCP 65.109.103.215 15001 => 10.42.42.22 51004
Sun Sep 3 10:00:16 2023 TCP 65.109.103.215 15001 => 10.42.42.22 51004
Sun Sep 3 10:01:36 2023 TCP 65.109.103.215 15001 => 10.42.42.22 51004
Sun Sep 3 10:03:05 2023 TCP 65.109.103.215 15001 => 10.42.42.22 51004
Sun Sep 3 09:57:33 2023 TCP 65.109.103.215 15001 => 10.42.43.26 51004
Sun Sep 3 09:57:35 2023 TCP 65.109.103.215 15001 => 10.42.43.26 51004
Sun Sep 3 10:02:13 2023 TCP 65.109.103.215 15001 => 10.42.43.26 51004
Sun Sep 3 10:02:14 2023 TCP 65.109.103.215 15001 => 10.42.43.26 51004
Sun Sep 3 10:02:15 2023 TCP 65.109.103.215 15001 => 10.42.43.26 51004
Sun Sep 3 10:02:17 2023 TCP 65.109.103.215 15001 => 10.42.43.26 51004
Sun Sep 3 10:02:07 2023 TCP 65.109.103.215 15001 => 10.42.45.25 51004
Sun Sep 3 09:56:45 2023 TCP 65.109.103.215 15001 => 10.42.46.22 51004
Sun Sep 3 09:56:46 2023 TCP 65.109.103.215 15001 => 10.42.46.22 51004
Sun Sep 3 09:58:37 2023 TCP 65.109.103.215 15001 => 10.42.46.22 51004
Sun Sep 3 09:59:02 2023 TCP 65.109.103.215 15001 => 10.42.49.30 51004
Sun Sep 3 10:00:36 2023 TCP 65.109.103.215 15001 => 10.42.49.30 51004
Sun Sep 3 09:54:56 2023 TCP 65.109.103.215 15001 => 10.42.54.26 51004
Sun Sep 3 09:55:05 2023 TCP 65.109.103.215 15001 => 10.42.54.26 51004
Sun Sep 3 09:55:31 2023 TCP 65.109.103.215 15001 => 10.42.54.26 51004
Sun Sep 3 09:55:33 2023 TCP 65.109.103.215 15001 => 10.42.54.26 51004
Sun Sep 3 09:55:59 2023 TCP 65.109.103.215 15001 => 10.42.54.26 51004
Sun Sep 3 09:56:23 2023 TCP 65.109.103.215 15001 => 10.42.54.26 51004
Sun Sep 3 09:56:51 2023 TCP 65.109.103.215 15001 => 10.42.54.26 51004
Sun Sep 3 09:56:52 2023 TCP 65.109.103.215 15001 => 10.42.54.26 51004
Sun Sep 3 09:58:21 2023 TCP 65.109.103.215 15001 => 10.42.54.26 51004
Sun Sep 3 09:58:22 2023 TCP 65.109.103.215 15001 => 10.42.54.26 51004
Sun Sep 3 09:59:42 2023 TCP 65.109.103.215 15001 => 10.42.54.26 51004
Sun Sep 3 09:59:59 2023 TCP 65.109.103.215 15001 => 10.42.54.26 51004
Sun Sep 3 10:01:31 2023 TCP 65.109.103.215 15001 => 10.42.54.26 51004
Sun Sep 3 10:01:34 2023 TCP 65.109.103.215 15001 => 10.42.54.26 51004
Sun Sep 3 09:57:32 2023 TCP 65.109.103.215 15001 => 10.42.59.15 51004
Sun Sep 3 09:57:33 2023 TCP 65.109.103.215 15001 => 10.42.59.15 51004
Sun Sep 3 09:57:35 2023 TCP 65.109.103.215 15001 => 10.42.59.15 51004
Sun Sep 3 10:02:14 2023 TCP 65.109.103.215 15001 => 10.42.59.15 51004
Sun Sep 3 10:02:14 2023 TCP 65.109.103.215 15001 => 10.42.59.15 51004
Sun Sep 3 10:02:15 2023 TCP 65.109.103.215 15001 => 10.42.59.15 51004
Sun Sep 3 10:02:17 2023 TCP 65.109.103.215 15001 => 10.42.59.15 51004
Sun Sep 3 09:57:59 2023 TCP 65.109.103.215 15001 => 10.42.60.11 51004
Sun Sep 3 10:02:37 2023 TCP 65.109.103.215 15001 => 10.42.60.11 51004
Sun Sep 3 09:57:13 2023 TCP 65.109.103.215 15001 => 10.9.11.7 6903
Sun Sep 3 09:57:14 2023 TCP 65.109.103.215 15001 => 10.9.11.7 6903
Sun Sep 3 09:57:06 2023 TCP 65.109.103.215 15001 => 172.18.0.4 10010
Sun Sep 3 10:00:49 2023 TCP 65.109.103.215 15001 => 172.18.0.4 10010
Sun Sep 3 09:58:44 2023 TCP 65.109.103.215 15001 => 192.168.31.172 17002
Sun Sep 3 09:57:43 2023 TCP 65.109.103.215 15001 => 10.42.22.22 51001
Sun Sep 3 09:57:46 2023 TCP 65.109.103.215 15001 => 10.42.22.22 51001
Sun Sep 3 10:02:20 2023 TCP 65.109.103.215 15001 => 10.42.22.22 51001
Sun Sep 3 09:58:41 2023 TCP 65.109.103.215 15001 => 10.42.23.25 51001
Sun Sep 3 09:56:37 2023 TCP 65.109.103.215 15001 => 10.42.24.22 51001
Sun Sep 3 10:02:11 2023 TCP 65.109.103.215 15001 => 10.42.27.28 51001
Sun Sep 3 10:02:14 2023 TCP 65.109.103.215 15001 => 10.42.27.28 51001
Sun Sep 3 10:02:15 2023 TCP 65.109.103.215 15001 => 10.42.27.28 51001
Sun Sep 3 10:02:17 2023 TCP 65.109.103.215 15001 => 10.42.27.28 51001
Sun Sep 3 09:58:53 2023 TCP 65.109.103.215 15001 => 10.42.29.22 51001
Sun Sep 3 09:58:54 2023 TCP 65.109.103.215 15001 => 10.42.29.22 51001
Sun Sep 3 09:59:45 2023 TCP 65.109.103.215 15001 => 10.42.31.24 51001
Sun Sep 3 09:59:46 2023 TCP 65.109.103.215 15001 => 10.42.31.24 51001
Sun Sep 3 10:02:36 2023 TCP 65.109.103.215 15001 => 10.42.31.24 51001
Sun Sep 3 09:57:28 2023 TCP 65.109.103.215 15001 => 10.42.33.23 51001
Sun Sep 3 10:02:09 2023 TCP 65.109.103.215 15001 => 10.42.33.23 51001
Sun Sep 3 09:55:24 2023 TCP 65.109.103.215 15001 => 10.42.34.25 51001
Sun Sep 3 09:57:08 2023 TCP 65.109.103.215 15001 => 10.42.36.21 51001
Sun Sep 3 09:56:35 2023 TCP 65.109.103.215 15001 => 10.42.38.23 51001
Sun Sep 3 09:56:40 2023 TCP 65.109.103.215 15001 => 10.42.41.31 51001
Sun Sep 3 09:56:43 2023 TCP 65.109.103.215 15001 => 10.42.41.31 51001
Sun Sep 3 09:58:39 2023 TCP 65.109.103.215 15001 => 10.42.41.31 51001
Sun Sep 3 09:58:41 2023 TCP 65.109.103.215 15001 => 10.42.41.31 51001
Sun Sep 3 09:58:57 2023 TCP 65.109.103.215 15001 => 10.42.43.27 51001
Sun Sep 3 09:57:51 2023 TCP 65.109.103.215 15001 => 10.42.44.21 51001
Sun Sep 3 09:57:51 2023 TCP 65.109.103.215 15001 => 10.42.47.21 51001
Sun Sep 3 09:59:16 2023 TCP 65.109.103.215 15001 => 10.42.47.21 51001
Sun Sep 3 10:02:30 2023 TCP 65.109.103.215 15001 => 10.42.47.21 51001
Sun Sep 3 10:02:33 2023 TCP 65.109.103.215 15001 => 10.42.49.26 51001
Sun Sep 3 10:00:42 2023 TCP 65.109.103.215 15001 => 10.42.50.26 51001
Sun Sep 3 09:57:15 2023 TCP 65.109.103.215 15001 => 10.42.51.23 51001
Sun Sep 3 10:00:21 2023 TCP 65.109.103.215 15001 => 10.42.56.48 51001
Sun Sep 3 10:01:53 2023 TCP 65.109.103.215 15001 => 10.42.56.48 51001
Sun Sep 3 10:01:55 2023 TCP 65.109.103.215 15001 => 10.42.56.48 51001
Sun Sep 3 09:57:38 2023 TCP 65.109.103.215 15001 => 10.42.60.12 51001
Sun Sep 3 09:57:40 2023 TCP 65.109.103.215 15001 => 10.42.60.12 51001
Sun Sep 3 10:00:33 2023 TCP 65.109.103.215 15001 => 10.9.11.7 6953
Sun Sep 3 10:00:38 2023 TCP 65.109.103.215 15001 => 10.9.11.7 6953
Sun Sep 3 09:54:55 2023 TCP 65.109.103.215 15001 => 10.100.97.104 40028
Sun Sep 3 09:55:01 2023 TCP 65.109.103.215 15001 => 10.100.97.104 40028
Sun Sep 3 09:55:02 2023 TCP 65.109.103.215 15001 => 10.100.97.104 40028
Sun Sep 3 09:55:04 2023 TCP 65.109.103.215 15001 => 10.100.97.104 40028
Sun Sep 3 09:55:29 2023 TCP 65.109.103.215 15001 => 10.100.97.104 40028
Sun Sep 3 10:02:57 2023 TCP 65.109.103.215 15001 => 10.100.97.104 40028
Sun Sep 3 10:00:51 2023 TCP 65.109.103.215 15001 => 192.168.7.105 15006
Sun Sep 3 10:00:22 2023 TCP 65.109.103.215 15001 => 10.9.11.7 6948
Sun Sep 3 10:01:48 2023 TCP 65.109.103.215 15001 => 10.9.11.7 6948
Sun Sep 3 10:01:51 2023 TCP 65.109.103.215 15001 => 10.9.11.7 6948
Sun Sep 3 09:59:06 2023 TCP 65.109.103.215 15001 => 192.168.31.186 18006
Sun Sep 3 09:59:20 2023 TCP 65.109.103.215 15001 => 10.111.40.239 40044
Sun Sep 3 09:57:02 2023 TCP 65.109.103.215 15001 => 10.106.233.115 40033

failed: no Sminer.Registered event found

Node mode: storage
Profile: testnet
nodeadm version: v0.5.3
Docker images:
config-gen: config-gen 1.5.0 0463ecad5706
chain: cess-node 0.7.6-d2220c01057 a1d3bedfa350
bucket: bucket v0.7.9 98ab5c0af899

++ 2024-02-06 17:16:22 Listening on port: 6000
++ 2024-02-06 17:16:22 RPC addresses: [ws://192.168.50.30:59944]
++ 2024-02-06 17:16:22 Bootnodes: [_dnsaddr.boot-bucket-testnet.cess.cloud]
++ 2024-02-06 17:16:24 Local peer id: 12D3KooWQRvE438TzxRd6yu9aPsYFpW4veoaY4QCgwgK257My4eu
++ 2024-02-06 17:16:24 Chain network: cess-testnet
++ 2024-02-06 17:16:24 P2P network: cess-testnet
++ 2024-02-06 17:16:24 Number of cpu cores used: 4
++ 2024-02-06 17:16:24 RPC address used: ws://192.168.50.30:59944
OK 2024-02-06 17:16:24 Synchronization main chain completed: 90058
++ 2024-02-06 17:16:24 Connected to 12D3KooWS8a18xoBzwkmUsgGBctNo6QCr6XCpUDR946mTBBUTe83 successfully
++ 2024-02-06 17:16:24 Connected to 12D3KooWDWeiiqbpNGAqA5QbDTdKgTtwX8LCShWkTpcyxpRf2jA9 successfully
++ 2024-02-06 17:16:24 Connected to 12D3KooWNcTWWuUWKhjTVDF1xZ38yCoHXoF4aDjnbjsNpeVwj33U successfully
XX 2024-02-06 17:16:30 [0x1ff2f18fc3a732febf6b4de77a389800fd7caba7b357a2ebd4bee18f2874ce1a] failed: no Sminer.Registered event found

'"bucket.space" must be a valid port'

after entering cess config set details I am getting bucket.space must be a valid port but in the config set it only asks for the 15001 port but its entering
image

connection failed

image
image

2024-02-24 03:27:03 💤 Idle (105 peers), best: #339358 (0x7de7…06e0), finalized #339356 (0x60c6…a51a), ⬇ 1.1MiB/s ⬆ 750.8kiB/s

plz support me to solve this error. Thank you so much

Docker logs not running

Hello. I would like to raise an issue when running docker logs. When I enter command, it shows nothing. I don't know if my storage node has not been set-up good but I am quite sure I did the right thing. My node is running because I was able to validate space. I cannot just check docker logs.
cess

Bucket container stops working after changing disk path

Hello there.
I updated disk path via cess config set restarted cess and it stopped working with following error

XX 2023-12-02 21:08:42 [Init Pois-2] check and restore sub acc files error: restore sub acc files error: open /opt/bucket-disk/cXfaZEondSacZb82LBa6J5JdHavryAgM6wT5oaWaCLc2aFt3Q/bucket/space/idle-files-1: no such file or directory

I have a suspicion that directory cXfaZEondSacZb82LBa6J5JdHavryAgM6wT5oaWaCLc2aFt3Q should be copied from old mount point to the new disk path. But it would worth to mention that during configuration setup or do it automatically. Haven't tested it so far.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.