Upload many ftp files at once? - file

I have about 2,000 small files. I want to upload them to a server using FileZilla and it keeps kicking me out and telling me this:
Status: Delaying connection for 1 second due to previously failed connection attempt...
Status: Resolving address of ....www.blabla.com
Status: Connecting to 10.10.10
Status: Connection established, waiting for welcome message...
Response: 220---------- Welcome to Pure-FTPd [privsep] ----------
Response: 220-You are user number 12 of 500 allowed.
Response: 220-Local time is now 14:46. Server port: 21.
Response: 220-This is a private system - No anonymous login
Response: 220 You will be disconnected after 3 minutes of inactivity.
Command: USER user2
Response: 331 User user2 OK. Password required
Command: PASS ********
Response: 421 I can't accept more than 5 connections as the same user
Is there a better way to upload many files?

Option 1 > Go to Site Manager > transfer settings > Check the limit number of simultaneous connections and give it 1 connection > reconnect
Option 2 > Change FTP password to break current connections > an then reconnect
both options will not working if your hosting server giving a limit for ftp user connections then you must contact your hosting provider or upgrade your account

The log just says that multiple connections are not allowed in your FTP. Make sure that there are not more than five persons connected at the same time.

Related

The directory service failed to open a TCP port for exclusive use in DSRM mode

I am trying to browse ntds.dit database file using LDAP in DSRM mode using dsamain command line utility tool as shown below:
dsamain /dbpath C:\snapshot\Windows\NTDS\ntds.dit /ldapport 5000
But it's giving me the error
The directory service failed to open a TCP port for exclusive use in DSRM mode.
One thing to note here, is that the same command with same file is working perfectly in normal mode.
What I have tried till now is:
Tried to host it on multiple ports
Tried to add all the ports in the inbound rule to allow the connection if in any case the port is blocked in DSRM mode.
Tried creating a new snapshot and mounting the same
Checked if any other process is using the same port but it was not the case and I have tried to use some many different random free ports.
But everything failed.
I am attaching the event trace below:
EVENTLOG (Warning): NTDS General / Security : 3051
The directory has been configured to not enforce per-attribute authorization during LDAP add operations. Warning events will
be logged, but no requests will be blocked.
This setting is not secure and should only be used as a temporary troubleshooting step. Please review the suggested mitigations in the link below.
For more information, please see https://go.microsoft.com/fwlink/?linkid=2174032.
EVENTLOG (Warning): NTDS General / Security : 3054
The directory has been configured to allow implicit owner privileges when initially setting or modifying the nTSecurityDescriptor
attribute during LDAP add and modify operations. Warning events will be logged, but no requests will be blocked.
This setting is not secure and should only be used as a temporary troubleshooting step. Please review the suggested mitigations in the link below.
For more information, please see https://go.microsoft.com/fwlink/?linkid=2174032.
EVENTLOG (Informational): NTDS General / Service Control : 1000
Microsoft Active Directory Domain Services startup complete
EVENTLOG (Warning): NTDS LDAP / LDAP Interface : 2509
The Directory Service failed to open a TCP port for exclusive use.
Additional Data:
Port number:
5002
Error Value:
0 The operation completed successfully.
EVENTLOG (Warning): NTDS LDAP / LDAP Interface : 2509
The Directory Service failed to open a TCP port for exclusive use.
Additional Data:
Port number:
5003
Error Value:
0 The operation completed successfully.
EVENTLOG (Warning): NTDS LDAP / LDAP Interface : 2509
The Directory Service failed to open a TCP port for exclusive use.
Additional Data:
Port number:
5002
Error Value:
0 The operation completed successfully.
EVENTLOG (Warning): NTDS LDAP / LDAP Interface : 2509
The Directory Service failed to open a TCP port for exclusive use.
Additional Data:
Port number:
5003
Error Value:
0 The operation completed successfully.

Failure writing file Log_File_Risk_Alert_Report : The permissions granted to user '' are insufficient for performing this operation

Context: I keep raising this error when I try to execute an SSRS Email or File Drop subscription - and I have no idea why. The empty string '' seems to imply I need to add some specific user information but I have no idea where.
I was able to send a test email through the Database Mail wizard in the management studio. I noticed in the SQL Server sysmail_event_log record for that event the last_mod_user was NTService\MSSQLSERVER. But the failed subscription execution attempts are showing up under the sa in the last_mod_user I suspect something is at play between this discrepancy but idk how to fix it.
The error description also reads:
The mail could not be sent to the recipients because of the mail
server failure. (Sending Mail using Account 4 (2022-04-22T17:41:01).
Exception Message: Cannot send mails to mail server. (The SMTP server
requires a secure connection or the client was not authenticated. The
server response was: 5.7.57 Client not authenticated to send mail.
[BN0P110CA0026.NAMP110.PROD.OUTLOOK.COM]). )
Questions: Can someone please assist?
Add the account to the Local Admin of the Machine to fix the Operation.Mail one

org.apache.curator.ConnectionState Connection timed out for connection string

I have been facing this issue for my Solr instance which is managed by Zookeeper.
It appears that Zookeeper is able to send requests to Zookeeper which momentarily accepts the request and then refuses it.
In Zookeeper logs, I have been seeing this error:
INFO org.apache.zookeeper.ZooKeeper.Client.environment:user.dir=/ [1635628661#qtp-2049348234-50]
INFO org.apache.zookeeper.ZooKeeper Initiating client connection, connectString=localhost:2181 sessionTimeout=150000 watcher=org.apache.curator.ConnectionState#c4f2fbd [1635628661#qtp-2049348234-50]
INFO org.apache.zookeeper.ClientCnxn Opening socket connection to server localhost/127.0.0.1:2181. Will not attempt to authenticate using SASL (unknown error) [1635628661#qtp-2049348234-50-SendThread(localhost:2181)]
INFO org.apache.zookeeper.ClientCnxn Socket connection established to localhost/127.0.0.1:2181, initiating session [1635628661#qtp-2049348234-50 SendThread(localhost:2181)]
ERROR org.apache.curator.ConnectionState Connection timed out for connection string (localhost:2181) and timeout (15000) / elapsed (15290) [1635628661#qtp-204934823450]
org.apache.curator.CuratorConnectionLossException: KeeperErrorCode = ConnectionLoss
at org.apache.curator.ConnectionState.checkTimeouts(ConnectionState.java:191)
at org.apache.curator.ConnectionState.getZooKeeper(ConnectionState.java:86)
at org.apache.curator.CuratorZookeeperClient.getZooKeeper(CuratorZookeeperClient.java:113)
at org.apache.curator.framework.imps.CuratorFrameworkImpl getZooKeeper(CuratorF
Any help is appreciated here.
According to log you have opened socket on localhost:2181, so line:
INFO org.apache.zookeeper.ClientCnxn Socket connection established to localhost/127.0.0.1:2181, initiating session [1635628661#qtp-2049348234-50 SendThread(localhost:2181)]
Is states like, ok, we found an opened socket, now we attempt to write some data. And it sends connection request sending sessionId and password. If session is not already established - it is sends 0 as session id, but sends password.
If you will enable debug output you would see in log then something like
Session establishment request sent on <remote address>
Log record you asking about -
ERROR org.apache.curator.ConnectionState Connection timed out for connection string (localhost:2181) and timeout (15000) / elapsed (15290) [1635628661#qtp-204934823450]
related to curator itself. If client not connected - it call checkTimeout() and if check timeout result is 'CONNECTION_TIMEOUT' generates record like above.
Not so much information but I try to guess there is zookeper on your localhost but connection rejected, may be password required or something else.
Hope it will help.
(my answer is based on curator code from master here -> https://github.com/apache/curator)

Do I realy need Idle Connection in Postgres?

I have a project in Spring Boot (1.5.1.RELEASE) which is using Postgres DB (9.1-901-1).
While I am running this application in production it will create upto 100 number of Idle connection in DB.
So I override the default configuration to control creating 'N' number of idle connection. Please check below configuration:
datasource:
driverClassName: org.postgresql.Driver
url: jdbc:postgresql://localhost:5432/db_name
username: root
password: root
tomcat:
# default value is 100 but postgres' default is 100 as well. To prevent "PSQLException: FATAL: sorry, too many
# clients already", we decrease the max-active value here. Which should be sufficient, by the way
max-active: 10
max-idle: 10
min-idle: 5
max-wait: 30000
time-between-eviction-runs-millis: 5000
min-evictable-idle-time-millis: 60000
jmx-enabled: true
Now Its creating 5 Idle connection to DB.
I am verifying that by executing below query.
select * from pg_stat_activity;
Now My question is, Do I really need 5 Idle connection for Production environment.
What will happen if I change my configuration like below? Will this work without any problem?
max-active: 1
max-idle: 1
min-idle: 0
And also would like to know how PgBouncer will help for this case? Is it necessary to have PgBouncer for Postgres?
The configuration you have proposed is definitely not recommended. A complete DB connection cycle will go through
Establish TCP connection
Validate the credentials
Connection is ready
Execute commands
Disconnect
By maintaining idle connections (connection pool) with the DB you are saving times spent steps 1-3 thus achieving better performance.
You should tune the settings on the DB based on the max instances of the microservices that will connect. for e.g. if max number of microservice instances is 5 and the service is configured to maintain 50 idle connetions then ensure that your DB is configured to cater to atleast 250 connections.
To arrive at min connection settings for the microservices you will need to do some tests based on your non functional requirements and load tests on the services.

Agent message code 20084. The process could not connect to Subscriber

All servers running SQL 2005
SQL server (NOLA) replicates to 35 remote locations (StoreXX).
Earlier this week, one publication started having problems connecting
to 30 of the 35 remote locations, with an error of:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date 2/4/2010 10:00:01 AM
Log Job History (NOLA-Closing_Balance-CB Defaults to Stores-R99S-
Store1-2790)
Step ID 2
Server NOLA
Job Name NOLA-Closing_Balance-CB Defaults to Stores-R99S-Store1-2790
Step Name Run agent.
Duration 00:31:47
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0
Message
2010-02-04 16:31:48.081 Parameter values obtained from agent profile:
-bcpbatchsize 2147473647
-commitbatchsize 100
-commitbatchthreshold 1000
-historyverboselevel 2
-keepalivemessageinterval 300
-logintimeout 15
-maxbcpthreads 1
-maxdeliveredtransactions 0
-pollinginterval 5000
-querytimeout 1800
-skiperrors
-transactionsperhistory 100
2010-02-04 16:31:48.081 Connecting to Subscriber 'R99S-Store1'
2010-02-04 16:31:48.440 Agent message code 20084. The process could
not connect to Subscriber 'R99S-Store1'.
2010-02-04 16:31:48.472 Category:NULL
Source: Microsoft SQL Native Client
Number: 10054
Message: TCP Provider: An existing connection was forcibly closed by
the remote host.
2010-02-04 16:31:48.472 Category:NULL
Source: Microsoft SQL Native Client
Number: 10054
Message: Communication link failure
2010-02-04 16:31:48.472 The agent failed with a 'Retry' status. Try to
run the agent at a later time.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The problem is only this one publication & not all subscriptions. I
have deleted a problem subscription & readded, same problem.
I have created another publication (same dB) & subscription (same &
new subscribers) with the same results (error above).
Now is where it gets weird…..
I created a new publication using a different dB on both the publisher
& subscriber & everything works fine.
I have had the network folks check what they need to check & have
googled until I am blue in the face.
Can anyone give me any insight into this issue.
AHIA,
Larry….

Resources