My vserver is running out of space. I noticed the traffic stats of apache are taking a lot of space away. I expect email logs, system logs, ... are using some space too.
Is there any way in plesk to delete all statistiks and logs older than a year (or a month)?
I appreciate your help!
The logs can be taken care of using the log rotation setting in Plesk. The location of the GUI for it depends on what version of plesk you are using.
v.10
http://www.hosting.com/support/plesk/log-rotation-in-plesk-10
v.9
Domains > domain.tld > Log Manager
As for the traffic retention, again it depends on what version of plesk as to it's location, but in Plesk 10 I have found the easiest way to deal with Traffic Stats retention is via the Service Plans section. (Actually prefer this for the plesk related logs as well, but you can do more with linux's logrotate than with plesk).
Service Plans > [Name of the plan you are editing] > Logs & Statistics tab
Related
So as the title says we deleted by mistake the StorageAccount before disabling the Automatic Backup. SQL keeps trying to do the backup anyway (as per the Event Log) but there is no way to disable it. When disabling on the Portal it says:
Provisioning failed. StorageAccount 'hfidiag756' associated with VM 'hfidb' for boot diagnostics encountered an error. Please look at the error code for more information about the error.. StorageAccountNotFound
I tried recreating that account "hfidiag756" but then the error is StorageInternalError.
Also tried via PowerShell and no luck.
Want to avoid having to recreate the VM.
Thanks
Recreating the storage account with the same name may partially help as you already did, try the bellow steps:
On the vault item dashboard, click All Settings to open the Settings blade.
Backup policy blade
On the Settings blade, click Backup policy to open that blade then check if you can edit the policy for the specific backup that's still running.
If you still get the error about storage, try stopping the protection set to the VM:
If you choose to stop protecting a virtual machine, you are asked if you want to retain the recovery points. There are two ways to stop protecting virtual machines:
The following link contains a tutorial to try it:
stop all future backup jobs and delete all recovery points, or
stop all future backup jobs but leave the recovery points
There is a cost associated with leaving the recovery points in storage. However, the benefit of leaving the recovery points is you can restore the virtual machine later, if desired. For information about the cost of leaving the recovery points, see the pricing details. If you choose to delete all recovery points, you cannot restore the virtual machine.
I was messing with the configuration of my local Bugzilla, and I changed the Bugzilla offline message from nothing to some text.
Now, it has logged me off and I can't go back in to change it, or find where it's storing the text in the database.
Unfortunately none of the solutions offered here or on the Bugzilla / Bugzilla tracking system were able to solve the problem.
The installation is IIS7.5 / Window Server 2008 R2 / ActivePerl.
Settings were changed manually in the /data/params file.
What is the easiest way to sync or replicate files over a network? I am running a few servers in a rack for load balancing and wish to mirror content.
For example, I have Server 1 where I do my FTP uploads to. Server 2 is another node. The manual way is for me to also do FTP uploads to Server 2 but I am sure it can be done automatically without my presence or without the user logged in.
I have tried SyncToy but it just doesn't run when the user is not logged in. I have to manually run it.
Are there better ways? I saw Microsoft DFS but it is just too complicated for me to set up.
Try SyncBack.
There's a light-weight version (SE) which is free and a Pro version.
Vista just finished one of its many updates. After restarting my computer I try connecting to SqlServer2008 instance with Sql Server Management Studio and I get this error:
Error connecting to '...\MSSQLSERVER2008'.
Additional information:
Login failed for user '...'. Reason: Server is in script upgrade mode. Only administrator can connect at this time. (Microsoft SQL Server, Error: 18401).
Pressing help gets me to an internet page saying there's no additional information.
Thx Vista & Updates. Anyone an idea because on the internet I can't find anything about this issue.
It appears This Guy was having the same problems as you and his only suggestion was to wait a few minutes before trying to log in again.
I have yet to see any type of Microsoft documentation about this, nor have I seen any forum posts which came to any sort of resolution concerning the same problem.
Check your event viewer. I had the same problem and found that (in my case) it was looking for a directory that didn't exist to perform an upgrade script. NO hint that there was any sort of problem in the dialog, but the event viewer showed clearly what the problem was.
jim
I had the same problem. Waiting until update was done did not help. Solution was, (after checking Windows eventlog) to set the folder rights. SQL-Express had no rights on the database folder, why ever. Something has mixed up the rights during the upgrade from WinXP to Win 7. That was it.
Adding a comment to this page since this is the top Google result for "script upgrade mode". It seems that a number of things can cause a SQL Server DB to go into this mode. In our shop we've run into these two cases in the past months:
Log shipping - Can't recall at what point of the process exactly the DB went into this mode, iirc it was when bringing it back up. The solution was just to wait it out.
Hard drive full - The DB went into this mode when it ran out of space. We're currently clearing up the drive, will come back with an update if waking it up turns out to be challenging.
Update: After freeing up disk space, it was a simple matter of setting the DB "Offline" and then "Online" to bring it back up.
We had the same issue, but needed to know what was going on in the background.
The db's were put into recovery mode, hence they had to recover. To assist we went to the SQL Server error log located where the system files (normally master, model, msdb...) are located, but under the log folder. In the ERRORLOG, we did a find on the word recovery and could watch the db's percentage recovered. Everything recovered normally, but it was much longer than expected.
The Reason for this is that the system reboot happens with important\necesssary softwares loaded and does all other operation later so that the booting happens faster.
Here in your case, the sql booting is happening as the start of SQL is not needed for system to start. I hope you are aware of DAC account(Dedicated Administrator Connection, Link) who has seperate connectivity and has ability to resolve issues even the whole SQL server is not responing. The SQL server is asking you either to wait or open the SQL with DAC account and stop the SQL update.
Solutions:
1) Wait until backround update completes
2) Open SQL using DAC account and kill all running processes
Another SSRS question here:
We have a development, a QA, a Prod-Backup and a Production SSRS set of servers.
On our production and prod-backup, SSRS will go to sleep if not used for a period of time.
This does not occur on our development or QA server.
In the corporate environment we're in, we don't have physical (or even remote login) access to these machines, and have to work with a team of remote administrators to configure our SSRS application.
We have asked that they fix, if possible, this issue. So far, they haven't been able to identify the issue, and I would like to know if any of my peers know the answer to this question. Thanks.
For anybody using the integrated webserver that is built into SQL Reporting Services (and hence IIS may not even be installed on the box), the setting to control this actually lives in:
C:\Program Files\Microsoft SQL Server\
MSRS10_50.MSSQLSERVER\Reporting Services\ReportServer\rsreportserver.config
Your directory may be different; version 10_50 maps to SQL 2008 R2.
You'll be looking for the setting called RecycleTime.
Default is 720 (12 hours). Setting it to 0 will disable.
In IIS, check the settings on the application pool that SSRS is running in. On the properties pane->Performance tab you can set the amount of time the worker process needs to be idle for before it shuts down. You can also disable this entirely.
I vaguely recall having problems with SSRS on one machine when we changed the "Enable HTTP Keep-Alives" setting in IIS. Try toggling that checkbox (I don't remember whether it was checked or unchecked when it caused us problems).